Mad Fap Entertainment Online Store Performance Report

Hi, this is a Work In Progress (WIP) for the latest project I am working on. My client is a friends record label called Mad Fap Entertainment. It is a bit more than a typical record label, it includes comedy and some other unique talented artists.

https://madfapentertainment.com/

ANALYZE

Mobile
69

Desktop
99

https://madfapentertainment.com/

0–49 50–89 90–100

Field DataThe Chrome User Experience Report does not have sufficient real-world speed data for this page.

Origin SummaryThe Chrome User Experience Report does not have sufficient real-world speed data for this origin.

Lab Data
First Contentful Paint
3.2 s

Speed Index
4.3 s

Largest Contentful Paint
4.9 s

Time to Interactive
5.7 s

Total Blocking Time
220 ms

Cumulative Layout Shift
0

OpportunitiesThese suggestions can help your page load faster. They don’t directly affect the Performance score.

Opportunity

Estimated Savings

Eliminate render-blocking resources
1.1 s

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

There are a number of WordPress plugins that can help you inline critical assets or defer less important resources. Beware that optimizations provided by these plugins may break features of your theme or plugins, so you will likely need to make code changes.

URLTransfer SizePotential Savings
…css/autoptimize_4137261….css

(madfapentertainment.com)
54.6 KB1,680 ms
/css?family=…

(fonts.googleapis.com)
1.9 KB780 ms
…minify/c7035.js

(madfapentertainment.com)
33.7 KB1,530 ms

Serve images in next-gen formats

0.98 s

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Consider using a plugin or service that will automatically convert your uploaded images to the optimal formats.

URLResource SizePotential Savings
…06/mockup-834b3e97-768×768.png

(cdn.shortpixel.ai)
293.7 KB219.9 KB
…06/mockup-033cfa77-768×768.png

(cdn.shortpixel.ai)
82 KB27 KB
…06/a026…_10-768×768.jpg

(madfapentertainment.com)
53.1 KB22.9 KB

Remove unused JavaScript

0.9 s

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Consider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your page. To identify plugins that are adding extraneous JS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the script. Look out for plugins that have many scripts in the list which have a lot of red in code coverage. A plugin should only enqueue a script if it is actually used on the page.

URLTransfer SizePotential Savings
…config/632…?v=2.9.18&r=stable

(connect.facebook.net)
129.8 KB112 KB
…minify/c7035.js

(madfapentertainment.com)
33.7 KB16.5 KB
/en_US/fbevents.js

(connect.facebook.net)
31.6 KB16.1 KB
…minify/d934a.js

(madfapentertainment.com)
19 KB11.7 KB
…plugins/identity.js?v=2.9.18

(connect.facebook.net)
11.6 KB10.1 KB
…minify/f9fb9.js

(madfapentertainment.com)
4.6 KB2.4 KB

Remove unused CSS

0.75 s

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Consider reducing, or switching, the number of WordPress plugins loading unused CSS in your page. To identify plugins that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a stylesheet if it is actually used on the page.

URLTransfer SizePotential Savings
…css/autoptimize_4137261….css

(madfapentertainment.com)
54.6 KB52 KB

Reduce initial server response time

0.02 s

Keep the server response time for the main document short because all other requests depend on it. Learn more.

Themes, plugins, and server specifications all contribute to server response time. Consider finding a more optimized theme, carefully selecting an optimization plugin, and/or upgrading your server.

DiagnosticsMore information about the performance of your application. These numbers don’t directly affect the Performance score.

Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URLPotential Savings
…v13/6xK3dSBYK….woff2

(fonts.gstatic.com)
0 ms
…v13/6xKydSBYK….woff2

(fonts.gstatic.com)
0 ms
…v13/6xKydSBYK….woff2

(fonts.gstatic.com)
0 ms

Serve static assets with an efficient cache policy 7 resources found

A long cache lifetime can speed up repeat visits to your page. Learn more.

Read about Browser Caching in WordPress.

URLCache TTLTransfer Size
…config/632…?v=2.9.18&r=stable

(connect.facebook.net)
20 m130 KB
/en_US/fbevents.js

(connect.facebook.net)
20 m32 KB
…plugins/identity.js?v=2.9.18

(connect.facebook.net)
20 m12 KB
…js/wp-emoji-release.min.js?ver=5.4.2

(madfapentertainment.com)
4 h5 KB
…05/cropped-Untitled-design-3.png

(cdn.shortpixel.ai)
29 d 23 h 59 m 39 s22 KB
…06/mockup-834b3e97-768×768.png

(cdn.shortpixel.ai)
29 d 23 h 59 m 41 s294 KB
…06/mockup-033cfa77-768×768.png

(cdn.shortpixel.ai)
29 d 23 h 59 m 46 s83 KB

Avoid chaining critical requests 7 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Maximum critical path latency: 830 ms

Initial Navigation

https://madfapentertainment.com

…css/autoptimize_4137261….css

(madfapentertainment.com)

– 80 ms, 54.61 KB

…minify/c7035.js

(madfapentertainment.com)

– 70 ms, 33.68 KB

…v13/6xK3dSBYK….woff2

(fonts.gstatic.com)

– 0 ms, 13.67 KB

…fonts/fa-solid-900.woff2

(madfapentertainment.com)

– 20 ms, 78.07 KB

…v13/6xKydSBYK….woff2

(fonts.gstatic.com)

– 0 ms, 13.46 KB

/css?family=…

(fonts.googleapis.com)

– 10 ms, 1.94 KB

…v13/6xKydSBYK….woff2

(fonts.gstatic.com)

– 0 ms, 13.57 KB

Keep request counts low and transfer sizes small 23 requests • 875 KB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource TypeRequestsTransfer Size
Total23874.7 KB
Image6454.1 KB
Script7235.3 KB
Font4118.8 KB
Stylesheet256.5 KB
Document18 KB
Other32 KB
Media00 KB
Third-party14616.6 KB

Largest Contentful Paint element 1 element found

This is the element that was identified as the Largest Contentful Paint. Learn More

Element
Bluntfield – Memoirs of a Blazer

<img width=”324″ height=”324″ src=”https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_324/https://madfapentertainment.com/wp-content/uploads/2020/06/a0266573855_10-324×324.jpg” class=”attachment-woocommerce_thumbnail size-woocommerce_thumbnail” alt=”Bluntfield – Memoirs of a Blazer” srcset=”https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_324/https://madfapentertainment.com/wp-content/uploads/2020/06/a0266573855_10-324×324.jpg 324w, https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_300/https://madfapentertainment.com/wp-content/uploads/2020/06/a0266573855_10-300×300.jpg 300w, https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_1024/https://madfapentertainment.com/wp-content/uploads/2020/06/a0266573855_10-1024×1024.jpg 1024w, https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_150/https://madfapentertainment.com/wp-content/uploads/2020/06/a0266573855_10-150×150.jpg 150w, https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_768/https://madfapentertainment.com/wp-content/uploads/2020/06/a0266573855_10-768×768.jpg 768w, https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_416/https://madfapentertainment.com/wp-content/uploads/2020/06/a0266573855_10-416×416.jpg 416w, https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_100/https://madfapentertainment.com/wp-content/uploads/2020/06/a0266573855_10-100×100.jpg 100w, https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_1200/https://madfapentertainment.com/wp-content/uploads/2020/06/a0266573855_10.jpg 1200w” sizes=”(max-width: 324px) 100vw, 324px”>

Avoid large layout shifts 1 element found

These DOM elements contribute most to the CLS of the page.

Element
Menu

<button class=”menu-toggle” aria-controls=”site-navigation” aria-expanded=”false”>

Passed audits (18)

Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Upload images directly through the media library to ensure that the required image sizes are available, and then insert them from the media library or use the image widget to ensure the optimal image sizes are used (including those for the responsive breakpoints). Avoid using `Full Size` images unless the dimensions are adequate for their usage. Learn More.

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Install a lazy-load WordPress plugin that provides the ability to defer any offscreen images, or switch to a theme that provides that functionality. Also consider using the AMP plugin.

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn more.

A number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your styles. You may also want to use a build process to do this minification up-front if possible.

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

A number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your scripts. You may also want to use a build process to do this minification up front if possible.

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn more.

Consider using an image optimization WordPress plugin that compresses your images while retaining quality.

Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

You can enable text compression in your web server configuration.

Preconnect to required origins

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn more.

Preload key requests

Consider using &lt;link rel=preload&gt; to prioritize fetching resources that are currently requested later in page load. Learn more.

Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more

Consider uploading your GIF to a service which will make it available to embed as an HTML5 video.

Avoids enormous network payloads Total size was 875 KB

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

Consider showing excerpts in your post lists (e.g. via the more tag), reducing the number of posts shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.

URLTransfer Size
…06/mockup-834b3e97-768×768.png

(cdn.shortpixel.ai)
294.2 KB
…config/632…?v=2.9.18&r=stable

(connect.facebook.net)
129.8 KB
…06/mockup-033cfa77-768×768.png

(cdn.shortpixel.ai)
82.6 KB
…fonts/fa-solid-900.woff2

(madfapentertainment.com)
78.1 KB
…css/autoptimize_4137261….css

(madfapentertainment.com)
54.6 KB
…06/a026…_10-768×768.jpg

(madfapentertainment.com)
53.7 KB
…minify/c7035.js

(madfapentertainment.com)
33.7 KB
/en_US/fbevents.js

(connect.facebook.net)
31.6 KB
…05/cropped-Untitled-design-3.png

(cdn.shortpixel.ai)
22.5 KB
…minify/d934a.js

(madfapentertainment.com)
19 KB

Avoids an excessive DOM size 185 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflowsLearn more.

StatisticElementValue
Total DOM Elements185
Maximum DOM Depth<br><span class="woocommerce-Price-currencySymbol"><br>12
Maximum Child Elements<br><body class="home archive post-type-archive post-type-archive-product wp-custom-logo wp-embed-responsive theme-storefront woocommerce woocommerce-page woocommerce-js storefront-align-wide right-sidebar woocommerce-active"><br>17

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app’s real-world performance during key user experiences. Learn more.

JavaScript execution time 0.8 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URLTotal CPU TimeScript EvaluationScript Parse
https://madfapentertainment.com558 ms221 ms12 ms
…minify/c7035.js

(madfapentertainment.com)
208 ms187 ms7 ms
…config/632…?v=2.9.18&r=stable

(connect.facebook.net)
204 ms148 ms39 ms
<br>Unattributable<br>190 ms5 ms1 ms
…minify/d934a.js

(madfapentertainment.com)
103 ms45 ms7 ms
/en_US/fbevents.js

(connect.facebook.net)
66 ms51 ms10 ms
…css/autoptimize_4137261….css

(madfapentertainment.com)
65 ms0 ms0 ms
…minify/f9fb9.js

(madfapentertainment.com)
50 ms27 ms4 ms

Minimizes main-thread work 1.5 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

CategoryTime Spent
Script Evaluation698 ms
Other277 ms
Style & Layout258 ms
Parse HTML & CSS94 ms
Script Parsing & Compilation87 ms
Rendering56 ms

Minimize third-party usage Third-party code blocked the main thread for 70 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-PartyTransfer SizeMain-Thread Blocking Time
Facebook174 KB73 ms
Google Fonts43 KB0 ms

Uses passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as `passive` to improve your page’s scroll performance. Learn more.

Avoids document.write()

For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.

The speed score is based on the lab data analyzed by Lighthouse.

Analysis time: 6/19/2020, 10:49:58 PM

Version: 6.0.0

99

https://madfapentertainment.com/

0–49 50–89 90–100

Field DataThe Chrome User Experience Report does not have sufficient real-world speed data for this page.[Image: :/a11860d1817047ebb41362d9a19e5a59]

Origin SummaryThe Chrome User Experience Report does not have sufficient real-world speed data for this origin.

Lab Data

First Contentful Paint

0.7 s

Speed Index

0.9 s

Largest Contentful Paint

0.9 s

Time to Interactive

0.9 s

Total Blocking Time

10 ms

Cumulative Layout Shift

0.001

OpportunitiesThese suggestions can help your page load faster. They don’t directly affect the Performance score.

Opportunity

Estimated Savings

Eliminate render-blocking resources

0.23 s

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

There are a number of WordPress plugins that can help you inline critical assets or defer less important resources. Beware that optimizations provided by these plugins may break features of your theme or plugins, so you will likely need to make code changes.

URLTransfer SizePotential Savings
…css/autoptimize_4137261….css

(madfapentertainment.com)
54.6 KB350 ms
/css?family=…

(fonts.googleapis.com)
1.9 KB230 ms
…minify/c7035.js

(madfapentertainment.com)
33.7 KB310 ms

Remove unused CSS

0.16 s

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Consider reducing, or switching, the number of WordPress plugins loading unused CSS in your page. To identify plugins that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a stylesheet if it is actually used on the page.

URLTransfer SizePotential Savings
…css/autoptimize_4137261….css

(madfapentertainment.com)
54.6 KB51.8 KB

DiagnosticsMore information about the performance of your application. These numbers don’t directly affect the Performance score.

Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URLPotential Savings
…v13/6xK3dSBYK….woff2

(fonts.gstatic.com)
0 ms
…v13/6xKydSBYK….woff2

(fonts.gstatic.com)
0 ms
…v13/6xKydSBYK….woff2

(fonts.gstatic.com)
0 ms

Serve static assets with an efficient cache policy 7 resources found

A long cache lifetime can speed up repeat visits to your page. Learn more.

Read about Browser Caching in WordPress.

URLCache TTLTransfer Size
…config/632…?v=2.9.18&r=stable

(connect.facebook.net)
20 m131 KB
/en_US/fbevents.js

(connect.facebook.net)
20 m32 KB
…plugins/identity.js?v=2.9.18

(connect.facebook.net)
20 m12 KB
…js/wp-emoji-release.min.js?ver=5.4.2

(madfapentertainment.com)
4 h5 KB
…05/cropped-Untitled-design-3.png

(cdn.shortpixel.ai)
29 d 23 h 59 m 39 s22 KB
…06/mockup-834b3e97-324×324.png

(cdn.shortpixel.ai)
29 d 23 h 59 m 56 s57 KB
…06/mockup-033cfa77-324×324.png

(cdn.shortpixel.ai)
29 d 23 h 59 m 56 s15 KB

Avoid chaining critical requests 7 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Maximum critical path latency: 980 ms

Initial Navigation

https://madfapentertainment.com

…v13/6xKydSBYK….woff2

(fonts.gstatic.com)

– 0 ms, 13.46 KB

…v13/6xKydSBYK….woff2

(fonts.gstatic.com)

– 0 ms, 13.57 KB

…css/autoptimize_4137261….css

(madfapentertainment.com)

– 80 ms, 54.61 KB

…v13/6xK3dSBYK….woff2

(fonts.gstatic.com)

– 0 ms, 13.67 KB

…fonts/fa-solid-900.woff2

(madfapentertainment.com)

– 270 ms, 78.08 KB

/css?family=…

(fonts.googleapis.com)

– 10 ms, 1.91 KB

…minify/c7035.js

(madfapentertainment.com)

– 60 ms, 33.68 KB

Keep request counts low and transfer sizes small 23 requests • 533 KB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource TypeRequestsTransfer Size
Total23533.2 KB
Script7236.6 KB
Font4118.8 KB
Image6111.5 KB
Stylesheet256.5 KB
Document17.9 KB
Other32 KB
Media00 KB
Third-party14313.4 KB

Largest Contentful Paint element 1 element found

This is the element that was identified as the Largest Contentful Paint. Learn More

Element

Avoid large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page.

Element
My account

<a href=”https://madfapentertainment.com/my-account/“>
Newsletter

<a href=”https://madfapentertainment.com/newsletter/“>
Mad Fap Entertainment Snapback Hat

<h2 class=”woocommerce-loop-product__title”>
Posts

<a href=”https://madfapentertainment.com/posts/“>
Cart

<a href=”https://madfapentertainment.com/cart/“>

Passed audits (21)

Properly size images Potential savings of 52 KB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Upload images directly through the media library to ensure that the required image sizes are available, and then insert them from the media library or use the image widget to ensure the optimal image sizes are used (including those for the responsive breakpoints). Avoid using `Full Size` images unless the dimensions are adequate for their usage. Learn More.

URLResource SizePotential Savings
…06/mockup-834b3e97-324×324.png

(cdn.shortpixel.ai)
56.6 KB27.8 KB
…05/cropped-Untitled-design-3.png

(cdn.shortpixel.ai)
21.9 KB17.3 KB
…06/mockup-033cfa77-324×324.png

(cdn.shortpixel.ai)
14.6 KB7.2 KB

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Install a lazy-load WordPress plugin that provides the ability to defer any offscreen images, or switch to a theme that provides that functionality. Also consider using the AMP plugin.

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn more.

A number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your styles. You may also want to use a build process to do this minification up-front if possible.

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

A number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your scripts. You may also want to use a build process to do this minification up front if possible.

Remove unused JavaScript Potential savings of 170 KB

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Consider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your page. To identify plugins that are adding extraneous JS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the script. Look out for plugins that have many scripts in the list which have a lot of red in code coverage. A plugin should only enqueue a script if it is actually used on the page.

URLTransfer SizePotential Savings
…config/632…?v=2.9.18&r=stable

(connect.facebook.net)
130.5 KB112.6 KB
…minify/c7035.js

(madfapentertainment.com)
33.7 KB16.5 KB
/en_US/fbevents.js

(connect.facebook.net)
32.2 KB16.4 KB
…minify/d934a.js

(madfapentertainment.com)
19 KB11.7 KB
…plugins/identity.js?v=2.9.18

(connect.facebook.net)
11.6 KB10.1 KB
…minify/f9fb9.js

(madfapentertainment.com)
4.6 KB2.4 KB

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn more.

Consider using an image optimization WordPress plugin that compresses your images while retaining quality.

Serve images in next-gen formats Potential savings of 39 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Consider using a plugin or service that will automatically convert your uploaded images to the optimal formats.

URLResource SizePotential Savings
…06/mockup-834b3e97-324×324.png

(cdn.shortpixel.ai)
56.6 KB38.8 KB

Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

You can enable text compression in your web server configuration.

Preconnect to required origins

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Initial server response time was short Root document took 510 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more.

Themes, plugins, and server specifications all contribute to server response time. Consider finding a more optimized theme, carefully selecting an optimization plugin, and/or upgrading your server.

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn more.

Preload key requests

Consider using &lt;link rel=preload&gt; to prioritize fetching resources that are currently requested later in page load. Learn more.

Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more

Consider uploading your GIF to a service which will make it available to embed as an HTML5 video.

Avoids enormous network payloads Total size was 533 KB

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

Consider showing excerpts in your post lists (e.g. via the more tag), reducing the number of posts shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.

URLTransfer Size
…config/632…?v=2.9.18&r=stable

(connect.facebook.net)
130.5 KB
…fonts/fa-solid-900.woff2

(madfapentertainment.com)
78.1 KB
…06/mockup-834b3e97-324×324.png

(cdn.shortpixel.ai)
57.1 KB
…css/autoptimize_4137261….css

(madfapentertainment.com)
54.6 KB
…minify/c7035.js

(madfapentertainment.com)
33.7 KB
/en_US/fbevents.js

(connect.facebook.net)
32.2 KB
…05/cropped-Untitled-design-3.png

(cdn.shortpixel.ai)
22.5 KB
…minify/d934a.js

(madfapentertainment.com)
19 KB
…06/a026…_10-324×324.jpg

(madfapentertainment.com)
15.5 KB
…06/mockup-033cfa77-324×324.png

(cdn.shortpixel.ai)
15.1 KB

Avoids an excessive DOM size 185 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflowsLearn more.

StatisticElementValue
Total DOM Elements185
Maximum DOM Depth<br><span class="woocommerce-Price-currencySymbol"><br>12
Maximum Child Elements<br><body class="home archive post-type-archive post-type-archive-product wp-custom-logo wp-embed-responsive theme-storefront woocommerce woocommerce-page woocommerce-js storefront-align-wide right-sidebar woocommerce-active"><br>17

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app’s real-world performance during key user experiences. Learn more.

JavaScript execution time 0.1 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URLTotal CPU TimeScript EvaluationScript Parse
https://madfapentertainment.com170 ms59 ms3 ms
…minify/c7035.js

(madfapentertainment.com)
58 ms52 ms1 ms

Minimizes main-thread work 0.4 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

CategoryTime Spent
Script Evaluation180 ms
Style & Layout74 ms
Other63 ms
Parse HTML & CSS25 ms
Script Parsing & Compilation19 ms
Rendering15 ms
Garbage Collection2 ms

Minimize third-party usage Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-PartyTransfer SizeMain-Thread Blocking Time
Facebook176 KB0 ms
Google Fonts43 KB0 ms

Uses passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as `passive` to improve your page’s scroll performance. Learn more.

Avoids document.write()

For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.

The speed score is based on the lab data analyzed by Lighthouse.

Analysis time: 6/19/2020, 10:49:58 PM

Version: 6.0.0

Leave a comment

Your email address will not be published. Required fields are marked *