Avoid chaining critical requests | ww.wp.xz.cn

Resolved srplcnr
(@srplcnr)

6 years ago

I got this error on Lighthouse. How can I fix?

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: 440 ms
Initial Navigation
/iletisim(www.cinar.av.tr)
…v9/pxiByp8kv….ttf(fonts.gstatic.com) – 10 ms, 66.05 KB
…v9/pxiByp8kv….ttf(fonts.gstatic.com) – 30 ms, 65.59 KB
…v9/pxiEyp8kv….ttf(fonts.gstatic.com) – 50 ms, 66.13 KB

The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)

Plugin Author Ahmed Kaludi
(@ahmedkaludi)

6 years ago

Can you please share the screenshots of the error that you have on your page?

Thread Starter srplcnr
(@srplcnr)

6 years ago

View post on imgur.com

https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Fwww.cinar.av.tr%2Filetisim&strategy=mobile&category=performance&category=accessibility&category=best-practices&category=seo&category=pwa&utm_source=lh-chrome-ext

Plugin Author Ahmed Kaludi
(@ahmedkaludi)

6 years ago

Its because we are loading the Google Fonts for the better design. I can tell you how to turn off but then it will not look good visually, perhaps you can try.

To do it: Go to AMP Options > Design > Typography > Turn Google fonts off.

But your intention is to take the Optimization to 90+ for that, you don’t need to focus on this, you need to reduce the TTFB and to do that, you should the static caching on your site which I think will take it to the 90+ score on performance.

Thread Starter srplcnr
(@srplcnr)

6 years ago

My caching plugin is active: AMP Cache (your plugin)
Should i do another thing?

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Avoid chaining critical requests’ is closed to new replies.

4 replies
2 participants
Last reply from: srplcnr
Last activity: 6 years ago
Status: resolved