0% found this document useful (0 votes)
84 views2 pages

PageSpeed Insights-After

The document summarizes the results of a PageSpeed Insights analysis of a website. It found that the first contentful paint took 2.8 seconds and time to interactive was 3.4 seconds. It provided opportunities to improve speed such as eliminating render-blocking resources and reducing initial server response time. Additional diagnostics were given around text visibility, caching, request counts and layout shifts.

Uploaded by

Kevin Mosh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
84 views2 pages

PageSpeed Insights-After

The document summarizes the results of a PageSpeed Insights analysis of a website. It found that the first contentful paint took 2.8 seconds and time to interactive was 3.4 seconds. It provided opportunities to improve speed such as eliminating render-blocking resources and reducing initial server response time. Additional diagnostics were given around text visibility, caching, request counts and layout shifts.

Uploaded by

Kevin Mosh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

PageSpeed Insights HOME

DOCS

https://www.insanefreedom.com/how-i-gained-99k-mo ANALYZE

MOBILE DESKTOP

77
https://www.insanefreedom.com/how-i-gained-99k-monthly-
viewers-on-pinterest/
0–49 50–89 90–100

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

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

Lab Data

First Contentful Paint 2.8 s Time to Interactive 3.4 s

Speed Index 6.1 s Total Blocking Time 20 ms

Largest Contentful Paint   4.0 s Cumulative Layout Shift   0

Values are estimated and may vary. The performance score is calculated directly from these
metrics. See calculator.

VIEW TREEMAP

Show audits relevant to: All FCP LCP TBT CLS

Opportunities — These suggestions can help your page load faster. They don't directly affect the
Performance score.

Opportunity Estimated Savings


Eliminate render-blocking resources 1.64 s
PageSpeed Insights HOME
DOCS

Reduce initial server response time 1.33 s

Serve images in next-gen formats 0.9 s

Properly size images 0.6 s

Reduce unused JavaScript 0.15 s

Diagnostics — More information about the performance of your application. These numbers don't directly
affect the Performance score.

Ensure text remains visible during webfont load

Serve static assets with an efficient cache policy


— 25 resources found

Avoid chaining critical requests


— 25 chains found

Keep request counts low and transfer sizes small


— 33 requests • 506 KiB

Largest Contentful Paint element


— 1 element found

Avoid large layout shifts


— 1 element found

Avoid long main-thread tasks


— 4 long tasks found

Avoid non-composited animations


— 4 animated elements found

Passed audits
(23)

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


Analysis time: 23/07/2021, 02:47:55
Run with Lighthouse 8.0.0 on Chrome 90.0.4430.97

What's New Web Performance


Read the latest Google Search Central blog Learn more about web performance tools at
posts about performance & speed. Google.

Give Feedback About PageSpeed Insights


Have specific, answerable questions about PageSpeed Insights analyzes the content of
using PageSpeed Insights? Ask your a web page, then generates suggestions to
question on Stack Overflow. For general make that page faster. See PageSpeed
feedback and discussion, start a thread in Insights documentation and release notes.
our mailing list.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy