Ye code, webfont load karte waqt text ko visible rakhne ke liye nahi hai. Ye code URLs mein specific patterns (like %3D, %3D%3D, &m=1, ?m=1) ko search kar raha hai aur agar woh patterns milte hain toh URL ko modify kar raha hai.
iska arth hia /?m=1 jo problem dikha raha hai vo bas dikhayega per us se appka koii effect nahi hoga speed per and mobile me /?m=1 appko ye code apne address bar me nahi dikhega ye replace karke only apka site address ko hi present karega
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 how to avoid chaining critical requests.FCPLCP
Maximum critical path latency: 865 ms
Initial Navigation
/?m=1
(skillgrowpro.blogspot.com)
…widgets/292…-widgets.js
- 7.16 ms, 58.61 KiB(www.blogger.com)
…v30/KFOmCnqEu….woff2
- 3.558 ms, 11.56 KiB(fonts.gstatic.com)
…v30/KFOlCnqEu….woff2
- 3.52 ms, 11.57 KiB(fonts.gstatic.com)
<script type='text/javascript'>
//<![CDATA[ var uri = window.location.toString(); if (uri.indexOf("%3D","%3D") > 0) { var clean_uri = uri.substring(0, uri.indexOf("%3D")); window.history.replaceState({}, document.title, clean_uri); } var uri = window.location.toString(); if (uri.indexOf("%3D%3D","%3D%3D") > 0) { var clean_uri = uri.substring(0, uri.indexOf("%3D%3D")); window.history.replaceState({}, document.title, clean_uri); } var uri = window.location.toString(); if (uri.indexOf("&m=1","&m=1") > 0) { var clean_uri = uri.substring(0, uri.indexOf("&m=1")); window.history.replaceState({}, document.title, clean_uri); } var uri = window.location.toString(); if (uri.indexOf("?m=1","?m=1") > 0) { var clean_uri = uri.substring(0, uri.indexOf("?m=1")); window.history.replaceState({}, document.title, clean_uri); } //]]> </script>after pasteing the upper code after the <head> result of Google insite
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 how to avoid chaining critical requests.FCPLCP
Maximum critical path latency: 789.93 ms
Initial Navigation
/?m=1
(skillgrowpro.blogspot.com)
…widgets/306…-widgets.js
- 10.943 ms, 58.60 KiB(www.blogger.com)
Comments
Post a Comment