Tools & Wizards About Us
waze.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

waze.com

Driving directions, live traffic & road conditions updates - Waze

Page Load Speed

20.5 sec in total

First Response

182 ms

Resources Loaded

11.4 sec

Page Rendered

8.9 sec

waze.com screenshot

About Website

Click here to check amazing Waze content for United States. Otherwise, check out these important facts you probably never knew about waze.com

Realtime driving directions based on live traffic updates from Waze - Get the best route to your destination from fellow drivers

Visit waze.com

Key Findings

We analyzed Waze.com page load time and found that the first response time was 182 ms and then it took 20.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

waze.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.9 s

3/100

10%

Network Requests Diagram

waze.com

182 ms

www.waze.com

818 ms

application-1a0df699de418bf8ebf9eb64d97d4f5ca8f3feb82967ac1e0b1770194e98a49a.css

374 ms

css

665 ms

vendor.legacy-6405b7987ede6130bc6fd6e0542a26d737e858bee0a0da369030ba65530f415c.js

597 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 72% of them (21 requests) were addressed to the original Waze.com, 14% (4 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Waze.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (42%)

Content Size

2.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waze.com main page is 2.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.9 kB

  • Original 15.8 kB
  • After minification 15.7 kB
  • After compression 4.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 10.9 kB or 69% of the original size.

Image Optimization

-1%

Potential reduce by 13.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Waze images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 713.2 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 340.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 713.2 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 357.9 kB

  • Original 442.5 kB
  • After minification 440.0 kB
  • After compression 84.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Waze.com needs all CSS files to be minified and compressed as it can save up to 357.9 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waze. According to our analytics all requests are already optimized.

Network Requests Diagram

waze.com

waze.com

182 ms

www.waze.com

www.waze.com

818 ms

application-1a0df699de418bf8ebf9eb64d97d4f5ca8f3feb82967ac1e0b1770194e98a49a.css

application-1a0df699de418bf8ebf9eb64d97d4f5ca8f3feb82967ac1e0b1770194e98a49a.css

374 ms

css

css

665 ms

vendor.legacy-6405b7987ede6130bc6fd6e0542a26d737e858bee0a0da369030ba65530f415c.js

vendor.legacy-6405b7987ede6130bc6fd6e0542a26d737e858bee0a0da369030ba65530f415c.js

597 ms

application-3ed2c4ec67b93278a0e45e8e97d4c0e93dc1cab496a0c29b58677facd6662dc4.js

application-3ed2c4ec67b93278a0e45e8e97d4c0e93dc1cab496a0c29b58677facd6662dc4.js

598 ms

analytics.js

analytics.js

5813 ms

wazelogo-54a4bf6b2793c2372642d6f8479e411384c2aaca12caedc9b30cad2335eb9a04.png

wazelogo-54a4bf6b2793c2372642d6f8479e411384c2aaca12caedc9b30cad2335eb9a04.png

5299 ms

iphone-96016d9f0409f62079d1716efcf1860144c535c4e513c1c5fb94fef4aba52a35.png

iphone-96016d9f0409f62079d1716efcf1860144c535c4e513c1c5fb94fef4aba52a35.png

5066 ms

screenshot-2ab76b7ecf6bea46e887f660c22fb510b344b9d8971bb495126fe2ad413b4e91.png

screenshot-2ab76b7ecf6bea46e887f660c22fb510b344b9d8971bb495126fe2ad413b4e91.png

6254 ms

sprites-s03cbf15c65-890feba8f6c6a12d6ded87c0e3fc130c56334bba958b2d0f35061421a510a170.png

sprites-s03cbf15c65-890feba8f6c6a12d6ded87c0e3fc130c56334bba958b2d0f35061421a510a170.png

6254 ms

real_time_updates-b57366538ec478bb86026d977becd769f951b06be5be02de7d3ce7b128f53eff.png

real_time_updates-b57366538ec478bb86026d977becd769f951b06be5be02de7d3ce7b128f53eff.png

6254 ms

reports_all_kinds-3628190a41bfe4b5c9090a0bbd184f9cec097aa47ba832befd1cee2fd0ba4586.png

reports_all_kinds-3628190a41bfe4b5c9090a0bbd184f9cec097aa47ba832befd1cee2fd0ba4586.png

6583 ms

map_editing-7df15c15f330a3b3dae4cd8978355ef4e77b1e6dc716cfc0c9f98b0f86f718db.png

map_editing-7df15c15f330a3b3dae4cd8978355ef4e77b1e6dc716cfc0c9f98b0f86f718db.png

6582 ms

social-fcb986640b0a07c5c197041b958d88a036ba1ff3c917998bd9ba3039f3eccec6.png

social-fcb986640b0a07c5c197041b958d88a036ba1ff3c917998bd9ba3039f3eccec6.png

6665 ms

fuel-806d1ba391833128050d8d9aed37a91761221e9d9c8afec10e4f7e11674b5814.png

fuel-806d1ba391833128050d8d9aed37a91761221e9d9c8afec10e4f7e11674b5814.png

6557 ms

footer-logo@2x-fd8d09a643d564a384f968f3e961e9a06374060146b0f5c6b532f8df3cd25755.png

footer-logo@2x-fd8d09a643d564a384f968f3e961e9a06374060146b0f5c6b532f8df3cd25755.png

6406 ms

country_by_ip

country_by_ip

1912 ms

cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff

cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff

2488 ms

DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff

DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff

2489 ms

MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff

MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff

3404 ms

k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff

k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff

3518 ms

fontawesome-webfont-ba0c59deb5450f5cb41b3f93609ee2d0d995415877ddfa223e8a8a7533474f07.woff

fontawesome-webfont-ba0c59deb5450f5cb41b3f93609ee2d0d995415877ddfa223e8a8a7533474f07.woff

1700 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1700 ms

get

get

1726 ms

collect

collect

642 ms

collect

collect

2200 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

99 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

79 ms

Accessibility Review

waze.com accessibility score

62

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

waze.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

waze.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waze.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Waze.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

waze.com

Open Graph description is not detected on the main page of Waze. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: