75 / 100
Should Fix:
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
- https://d26tpo4cm8sb6k.cloudfront.net/js/common.js
Optimize CSS Delivery of the following:
- https://d26tpo4cm8sb6k.cloudfront.net/style-mobile2.css
Show how to fix
Consider Fixing:
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
- https://ssl.google-analytics.com/ga.js (2 hours)
Show how to fix
Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 415B (12% reduction).
- Minifying https://d26tpo4cm8sb6k.cloudfront.net/style-mobile2.css could save 415B (12% reduction) after compression.
Show how to fix
7 Passed Rules
99 / 100
Consider Fixing:
Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
- The tap target
<a href="/about-us.html#privacy">privacy policies</a> and 2 others are close to other tap targets.
Show how to fix
4 Passed Rules
Show details
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
90 / 100
Consider Fixing:
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
- https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
- https://ssl.google-analytics.com/ga.js (2 hours)
Show how to fix
Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 401B (11% reduction).
- Minifying https://d26tpo4cm8sb6k.cloudfront.net/style2.css could save 401B (11% reduction) after compression.
Show how to fix
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
- https://d26tpo4cm8sb6k.cloudfront.net/js/common.js
Optimize CSS Delivery of the following:
- https://d26tpo4cm8sb6k.cloudfront.net/style2.css
Show how to fix
7 Passed Rules
* The results are cached for 30s. If you have made changes to your page, please wait for 30s before re-running the test.
