PageSpeed FAQS For Supersonic Pages

Why don't analytics PageSpeed numbers match PageSpeed scores?

Why don't analytics PageSpeed scores match the PageSpeed tool?

According to Google Analytics, the PageSpeed score for the page above is 88/100 but, in reality PageSpeed for this page is 64/100 for mobile users and 77/100 for desktop users. Don't be a sucker for analytics data dung! The only source for accurate up-to-date PageSpeed data is Google's NEW AND IMPROVED PageSpeed Insights tool. PageSpeed data from analytics and other sources is not always accurate or updated.

How fast should pages load?

As Matt Cutts recently pointed out, websites perform differently in different parts of the world. Ideally pages should load faster than the median load time in the country or region they target.

Where do I find the median page load time for my country or region of the world?

2013 Median Page Load Times: North America
- US 2.4 seconds desktop / 2.6 seconds mobile
- Canada 2.4 seconds desktop / 3.6 seconds mobile
- Mexico 3.8 seconds desktop / 4.5 seconds mobile
- Cuba 17.5 seconds desktop / 4.5 seconds mobile
- Bahamas 3.3 seconds desktop / 4.5 seconds mobile

2013 Median Page Load Times: Europe
- Czech Republic 1.6 seconds desktop / 3.4 seconds mobile
- Netherlands 1.8 seconds desktop / 3.1 seconds mobile
- Sweden 1.8 seconds desktop / 3.2 seconds mobile
- Russia 2.4 seconds desktop / 4.8 seconds mobile
- Germany 2.5 seconds desktop / 3.0 seconds mobile
- UK 2.5 seconds desktop / 3.6 seconds mobile
- Poland 2.7 seconds desktop / 4.7 seconds mobile
- Italy 3.3 seconds desktop / 5 seconds mobile
- Spain 3.2 seconds desktop / 5.3 seconds mobile

2013 Median Page Load Times: Asia
- South Korea 1.4 seconds desktop / 1.7 seconds mobile
- Japan 1.8 seconds desktop / 3.0 seconds mobile
- Russia 2.4 seconds desktop / 4.8 seconds mobile
- China 2.5 seconds desktop / 3.7 seconds mobile
- Viet Nam 2.5 seconds desktop /4.5 seconds mobile
- Thailand 3.7 seconds desktop / 5.8 seconds mobile
- Indonesia 7.4 seconds desktop / 5.1 seconds mobile
- India 5.1 seconds desktop / 5.8 seconds mobile
- Saudi Arabia 4.0 seconds desktop / 6.7 seconds mobile
- Pakistan 6.4 seconds desktop / 8.0 seconds mobile
- Iraq 5.5 seconds desktop / 5.9 seconds mobile
- Iran 6.1 seconds desktop / 9.5 seconds mobile
- Syria 8.1 seconds desktop / 9.1 seconds mobile

2013 Median Page Load Times: South America
- Chile 4.0 seconds desktop / 5.5 seconds mobile
- Brazil 4.7 seconds desktop / 7.7 seconds mobile
- Peru 4.3 seconds desktop / 8.5 seconds mobile
- Argentina 5.3 seconds desktop / 7.3 seconds mobile

2013 Median Page Load Times: Australia
- Australia 3.5 seconds desktop / 4.4 seconds mobile

2013 Median Page Load Times: Africa
- Morocco 3.5 seconds desktop / 5.0 seconds mobile
- South Africa 4.8 seconds desktop / 5.3 seconds mobile
- Algeria 5.1 seconds desktop / 7.8 seconds mobile
- Egypt 5.9 seconds desktop / 7.7 seconds mobile
- Kenya 7.7 seconds desktop / 11.4 seconds mobile

The list above provides the most recent median page load times as of 2013 from Google.

How do I compare pages with the same PageSpeed score to see which loads faster?

PageSpeed Insights is a great general purpose litmus test for improving PageSpeed but it only considers the network-independent aspects of page performance. To get down and dirty with respect to network performance and other speed related issues, you need to experience load times from the user perspective. To actually time pages via different browsers from various locations, use tools like WebPageTest.org or Pingdom. For instance, let's compare real load times, PageSpeed and speed index numbers for pages with Google Analytics, an optimized version of Google Analtyics and Google Tag Manager.

Load Time / Speed Index / PageSpeed
- empty page .461 seconds / 400 / 100/100
- custom analytics .619 seconds / 600 / 100/100
- standard analytics .808 seconds / 800 / 100/100
- tag manager .881 seconds / 900 / 100/100

Result: All of the URLs tested above have the same PageSpeed score of 100/100. However, from a user perspective the empty page has the best Speed Index score and loaded fastest.

Why are pages with asynchronous JavaScript slower than pages without JavaScript?

1. Not all browsers support asynchronous attributes.

2. When asynchronous scripts arrive during page load, browsers have to stop rendering the page in order to parse and execute scripts.

Even small things, like white space and HTML comments decrease page performance and increase load times. Scripts with ASYNC attributes like social media buttons and analytics tracking codes increase load times from a user perspective. It is always best to avoid including any unnecessary code or scripts even if they include the ASYNC attribute. Asynchronous scripts still impact performance.

 

Leave a Reply