if a website loads ads through client's (Ads service provider) interfaces. These ads are only displayed to customers who have an AdBlocker enabled, are using the Firefox browser or non Consent.
This ad loads only after the entire web page has been completely retrieved. This results in a "layout shift".
Q) Is this layout shift not considered in the current PageSpeed Insight lab data? Google Bot (PageSpeed Insight) is probably not running Adblocker or Firefox.
Can anyone help me on this?
Start the Google Developer tool in Chrome Browser (Ctrl+Shift+ I or F12 For Windows).
Select the network tab.
Reload the page.
Check if those ads resources are loading or not. If yes then Google is taking those resources into account while calculating the PageSpeed score.
Is it considered in lab data? - probably not (depending on your timings).
However as far as the upcoming Core Web Vitals update it will still affect your score there.
You see Google will user the Chrome User Experience dataset (CrUX dataset) to determine your CLS etc.
The CrUX dataset is collected from real world users (who may be using an ad blocker!).
The big difference is that when collecting the Cumulative Layout Shift (CLS) data for the CrUX dataset Google actually monitors the page for Layout Shifts until page unload.
So if you have a layout shift at any point while someone is using the site it will affect your CLS score.
If you have enough traffic you can see this data under then "Origin Summary" and or "Field Data" sections on your Lighthouse report.
Related
I've tried it with chrome browser and also microsoft edge still doesn't show up. Is there another solution so that an image or art clip appears on the website
Thanks
http://delphi-z.ru/index.php?do=register
When using WebPageTest it is possible to use custom scripts to set cookies. Is it possible to do the same on PageSpeed Insights or lighthouse?
For example in the European Union you may want to set cookies to disable the cookie consent popup which will not appear for repeat users who have already consented to the website's cookie policy.
Page Speed Insights
Page Speed Insights (PSI) is designed for simulating a first time user to the site, so your cookies popup would always show.
It does not cache cookies or anything else. There is no way to send cookies to PSI.
Lighthouse in the browser
If you are using Lighthouse in the browser simply untick the "Clear Storage" option in the top bar (you may have to click the gear icon top right to reveal this) and at that point run the page twice (once to set the cache), cookies will be stored and you will record a run with cached images, files etc.
If you wanted to create a run where cookies are stored but nothing else is cached you could go to the application tab in developer tools and remove everything other than the cookies.
However as this is not indicative of a real world scenario I do not see the benefit and is only included as it answers the original question.
Lighthouse CLI + Puppeteer
Your final option for complete control would be to run Lighthouse CLI on your own machine.
The source code for Lighthouse is available on GitHub, takes a short while to set up, installing chromium etc. but it is worth it.
At that point you have more control, if you partner it with Puppeteer then you have all the control to set individual cookies etc.
However it does appear that you should be able to pass cookies directly to Lighthouse via config according to this thread, but it might not work and ultimately ends up recommending puppeteer. Perhaps that is a feature that will get improved upon soon.
I recently released a chrome extension new tab, and I wanted to check the download/usage statistics.
I added both google analytics and checked the chrome web store stats. The values are extremely different. Here they are (for the same app):
Here is my extension on the web store:
https://chrome.google.com/webstore/detail/perspective-new-tab/hehnfhfmcifhbgkefjbfbaefhddlpnjj
My question: why are these values so different? They are off by a factor of 10. Which one (if any) is correct, and is there some way I can know for sure?
Thanks!
As stated in this post, sometimes it takes many days for stats to show, and some days are never updated.
If you link your extension with google analytics, you can then see installs from analytics but its not the same, as the chrome stats also substract uninstalls (not tracked in analytics).
You may also check this link for additional reference.
I am developing a responsive website. For each and every change I made in javascript, css & html file, I need to test it in all possible screen size in portrait and landscape mode. Normally we used to test it in 3 to 5 different browser window size, and in portrait & landscape. I felt changing screensize and orientation again and again is a tedious job. So planned to write a tool, which will open multiple browser windows in a different screen size with the given url loaded in it. Any idea, or advice how to start this?
PS. If you are voting for deleting this question, please consider commenting with some suggestion how I can start, or is there any free tool available for this.
Thanks in advance.
There are number of great tools and services for helping test a website in just about every possible OS/browser/size these days.
BrowserStack.com allows you to pull up your website on nearly every combination of OS/browser/size and use the site to see how elements and features perform. There are other many other services that do this.
Another option would be a browser extension/plugin like Chrome's Window Resizer. It allows you to quickly toggle between common (and custom) window sizes. This is the most manual of the three options here, and the only free option.
One final option is Adobe's Edge Inspect. This app allows you to connect several devices to your computer and simultaneously browse a site across each of the devices. It also allows you to remote inspection on each of the connected devices.
Tools like Selenium can drive browsers and resize them as needed. Depending on the language of your choice, google for something like: selenium resize browser (language of your choice)
I was thinking to add meta tag always in all the websites.
That will trigger google chorme frame to load for users who already installed. I can see the benefits but is there any concerns or facts that I should know before I do that?
Testing in google chrome is enough or testing in google chrome frame explicitly required?
Thanks
Note: please do not mention current know problems "print" and "download" issue. I'm sure those will get fixed soon :)
The only argument against chrome frame that I have seen so far is Microsoft's - "Google Chrome Frame running as a plugin has doubled the attach area for malware and malicious scripts."
Also, you may run into problems with frames. If you have chrome frame on your page and someone has that page iframed on their site you may run into some problems. More info:
http://groups.google.com/group/google-chrome-frame/browse_thread/thread/d5ffe442658bc60e/e6d7a4c1c179c931?lnk=gst&q=iframe
You should only need to test in Chrome Frame for (X)HTML, CSS, and JavaScript...basic stuff. If you are using AJAX (while trying not to break the back button), worried about caching, cookies (accessed via javascript), or other potentially browser-specific browser interactions I suggest testing on the IE+CF platform...at least until the CF team announces 100% interoperability between CF and IE.
Check out the CF Google group for more issues.
Are there any concerns or facts you should know? Yes: Not everyone has Google Chrome Frame installed.
You are adding a new user agent that you will need to test and debug against, without removing the need to test and debug the user experience for other browsers (notably plain IE by itself).
If you don't make the IE user experience equivalent to the Google Chrome experience, then you are alienating a significant percentage of users. Depending on your website and its expected users, the impact of this may range from undesirable to unacceptable. If you do make the user experience equivalent, then there is no point in adding the meta tag.