54 / 100
Should Fix:
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://bat.bing.com/bat.js (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/amazing-checkmark.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/amazing-waves-bottom.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/amazing-waves-top-light.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/amazing-waves-top.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/illustrations/amazing-laptop.gif (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/illustrations/amazing-papers.gif (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/illustrations/amazing-world.gif (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/illustrations/amazing-you.gif (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/lock.svg (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/our-blog.jpg (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/our-courses.jpg (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/puff.svg (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/facebook.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/google%2B.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/instagram.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/linkedin.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/twitter.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/youtube.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/world-map.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/webcampus/fonts/amazing-fonts.css (expiration not specified)
- https://s3.amazonaws.com/amazing.images/webcampus/logo-white.svg (expiration not specified)
- https://static.tapfiliate.com/tapfiliate.js (expiration not specified)
- https://static.hotjar.com/c/hotjar-20374.js?sv=3 (60 seconds)
- https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js (5 minutes)
- https://www.googletagmanager.com/gtm.js?id=GTM-NMB4HZ (15 minutes)
- https://connect.facebook.net/en_US/fbds.js (20 minutes)
- https://connect.facebook.net/en_US/fbevents.js (20 minutes)
- https://connect.facebook.net/en_US/sdk.js (20 minutes)
- https://dnn506yrbagrg.cloudfront.net/pages/scripts/0014/8529.js?409941 (60 minutes)
- https://external-atl3-1.xx.fbcdn.net/safe_image.php?d=AQANbI6YD6K_s-m0&w=158&h=158&url=https%3A%2F%2Fi.ytimg.com%2Fvi%2FY0dLjr4Ob1Q%2Fmaxresdefault.jpg&cfs=1&upscale=1 (2 hours)
- https://www.google-analytics.com/analytics.js (2 hours)
Show how to fix
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 12 blocking script resources and 5 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://code.jquery.com/jquery-1.11.2.min.js
- https://amazing.com/js/vendor/modernizr.js
- https://amazing.com/js/mixpanel-events.js
- https://amazing.com/js/amazing-mechanics.js
- https://amazing.com/js/mailcheck.min.js
- https://amazing.com/js/headroom.min.js
- https://klaviyo.com/media/js/public/klaviyo_subscribe.js
- https://amazing.com/js/covervid.js
- https://amazing.com/js/masthead.js
- https://amazing.com/js/teletype.min.js
- https://amazing.com/js/waypoints.min.js
- https://amazing.com/js/counterup.min.js
Optimize CSS Delivery of the following:
- https://amazing.com/css/foundation.css
- https://amazing.com/css/amazing-stylesheet.css
- https://fonts.googleapis.com/css?family=Oswald:300,400,700|Asap:400,700,400italic|Montserrat:400,700|Rajdhani|Roboto:400,700|Khand:600,700
- https://s3.amazonaws.com/amazing.images/webcampus/fonts/amazing-fonts.css
- https://a.klaviyo.com/media/css/public/klaviyo_subscribe.css
Show how to fix
Consider Fixing:
Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 36.8KiB (78% reduction).
- Compressing https://s3.amazonaws.com/amazing.images/webcampus/fonts/amazing-fonts.css could save 32.6KiB (83% reduction).
- Compressing https://s3.amazonaws.com/amazing.images/webcampus/logo-white.svg could save 1.3KiB (51% reduction).
- Compressing https://s3.amazonaws.com/amazing.images/frontend/puff.svg could save 1KiB (72% reduction).
- Compressing https://s3.amazonaws.com/amazing.images/frontend/lock.svg could save 689B (46% reduction).
- Compressing https://b.frstre.com/?v1.2 could save 611B (46% reduction).
- Compressing https://beacon.tapfiliate.com/?v1.2 could save 611B (46% reduction).
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 6.2KiB (12% reduction).
- Minifying https://s3.amazonaws.com/amazing.images/webcampus/fonts/amazing-fonts.css could save 4.6KiB (12% reduction).
- Minifying https://amazing.com/css/amazing-stylesheet.css could save 1.5KiB (11% reduction) after compression.
Show how to fix
Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 1.1KiB (13% reduction).
- Minifying https://amazing.com/ could save 1.1KiB (13% reduction) after compression.
Show how to fix
Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 944B (20% reduction).
- Minifying https://amazing.com/js/headroom.min.js could save 944B (20% reduction) after compression.
Show how to fix
Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
- Only about 9% of the final above-the-fold content could be rendered with the full HTML response snapshot:17.
Show how to fix
3 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="https://m.face…amazing.com%2F" class="_5pcq">3 hrs</a>
is close to 1 other tap targets.
- The tap target
<a href="https://m.face…amazing.com%2F"></a>
is close to 1 other tap targets.
Show how to fix
5 Passed Rules
Show details
Avoid app install interstitials that hide content
Your page does not appear to have any app install interstitials that hide a significant amount of content. Learn more about the importance of avoiding the use of app install interstitials.
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.
73 / 100
Should Fix:
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://bat.bing.com/bat.js (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/amazing-checkmark.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/amazing-waves-bottom.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/amazing-waves-top-light.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/amazing-waves-top.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/illustrations/amazing-laptop.gif (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/illustrations/amazing-papers.gif (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/illustrations/amazing-world.gif (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/illustrations/amazing-you.gif (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/lock.svg (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/our-blog.jpg (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/our-courses.jpg (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/puff.svg (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/facebook.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/google%2B.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/instagram.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/linkedin.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/twitter.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/social/youtube.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/frontend/world-map.png (expiration not specified)
- https://s3.amazonaws.com/amazing.images/webcampus/fonts/amazing-fonts.css (expiration not specified)
- https://s3.amazonaws.com/amazing.images/webcampus/logo-white.svg (expiration not specified)
- https://static.tapfiliate.com/tapfiliate.js (expiration not specified)
- https://static.hotjar.com/c/hotjar-20374.js?sv=3 (60 seconds)
- https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js (5 minutes)
- https://www.googletagmanager.com/gtm.js?id=GTM-NMB4HZ (15 minutes)
- https://connect.facebook.net/en_US/fbds.js (20 minutes)
- https://connect.facebook.net/en_US/fbevents.js (20 minutes)
- https://connect.facebook.net/en_US/sdk.js (20 minutes)
- https://dnn506yrbagrg.cloudfront.net/pages/scripts/0014/8529.js?409941 (60 minutes)
- https://external-atl3-1.xx.fbcdn.net/safe_image.php?d=AQANbI6YD6K_s-m0&w=158&h=158&url=https%3A%2F%2Fi.ytimg.com%2Fvi%2FY0dLjr4Ob1Q%2Fmaxresdefault.jpg&cfs=1&upscale=1 (2 hours)
- https://www.google-analytics.com/analytics.js (2 hours)
Show how to fix
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 12 blocking script resources and 5 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://code.jquery.com/jquery-1.11.2.min.js
- https://amazing.com/js/vendor/modernizr.js
- https://amazing.com/js/mixpanel-events.js
- https://amazing.com/js/amazing-mechanics.js
- https://amazing.com/js/mailcheck.min.js
- https://amazing.com/js/headroom.min.js
- https://klaviyo.com/media/js/public/klaviyo_subscribe.js
- https://amazing.com/js/covervid.js
- https://amazing.com/js/masthead.js
- https://amazing.com/js/teletype.min.js
- https://amazing.com/js/waypoints.min.js
- https://amazing.com/js/counterup.min.js
Optimize CSS Delivery of the following:
- https://amazing.com/css/foundation.css
- https://amazing.com/css/amazing-stylesheet.css
- https://fonts.googleapis.com/css?family=Oswald:300,400,700|Asap:400,700,400italic|Montserrat:400,700|Rajdhani|Roboto:400,700|Khand:600,700
- https://s3.amazonaws.com/amazing.images/webcampus/fonts/amazing-fonts.css
- https://a.klaviyo.com/media/css/public/klaviyo_subscribe.css
Show how to fix
Consider Fixing:
Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 36.8KiB (78% reduction).
- Compressing https://s3.amazonaws.com/amazing.images/webcampus/fonts/amazing-fonts.css could save 32.6KiB (83% reduction).
- Compressing https://s3.amazonaws.com/amazing.images/webcampus/logo-white.svg could save 1.3KiB (51% reduction).
- Compressing https://s3.amazonaws.com/amazing.images/frontend/puff.svg could save 1KiB (72% reduction).
- Compressing https://s3.amazonaws.com/amazing.images/frontend/lock.svg could save 689B (46% reduction).
- Compressing https://b.frstre.com/?v1.2 could save 611B (46% reduction).
- Compressing https://beacon.tapfiliate.com/?v1.2 could save 611B (46% reduction).
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 6.2KiB (12% reduction).
- Minifying https://s3.amazonaws.com/amazing.images/webcampus/fonts/amazing-fonts.css could save 4.6KiB (12% reduction).
- Minifying https://amazing.com/css/amazing-stylesheet.css could save 1.5KiB (11% reduction) after compression.
Show how to fix
Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 1.1KiB (13% reduction).
- Minifying https://amazing.com/ could save 1.1KiB (13% reduction) after compression.
Show how to fix
Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 944B (20% reduction).
- Minifying https://amazing.com/js/headroom.min.js could save 944B (20% reduction) after compression.
Show how to fix
Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
- Only about 9% of the final above-the-fold content could be rendered with the full HTML response snapshot:17.
Show how to fix
3 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.