20.5 sec in total
182 ms
11.4 sec
8.9 sec
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.comWe 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 an excellent result, as only a small number of websites can load faster.
waze.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value5.6 s
17/100
25%
Value10.6 s
7/100
10%
Value1,150 ms
22/100
30%
Value0
100/100
15%
Value17.9 s
3/100
10%
182 ms
818 ms
374 ms
665 ms
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 size can be reduced by 1.1 MB (42%)
2.6 MB
1.5 MB
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.
Potential reduce by 10.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.
Potential reduce by 13.3 kB
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.
Potential reduce by 713.2 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.
Potential reduce by 357.9 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.
We found no issues to fix!
18
18
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.
waze.com
182 ms
www.waze.com
818 ms
application-1a0df699de418bf8ebf9eb64d97d4f5ca8f3feb82967ac1e0b1770194e98a49a.css
374 ms
css
665 ms
vendor.legacy-6405b7987ede6130bc6fd6e0542a26d737e858bee0a0da369030ba65530f415c.js
597 ms
application-3ed2c4ec67b93278a0e45e8e97d4c0e93dc1cab496a0c29b58677facd6662dc4.js
598 ms
analytics.js
5813 ms
wazelogo-54a4bf6b2793c2372642d6f8479e411384c2aaca12caedc9b30cad2335eb9a04.png
5299 ms
iphone-96016d9f0409f62079d1716efcf1860144c535c4e513c1c5fb94fef4aba52a35.png
5066 ms
screenshot-2ab76b7ecf6bea46e887f660c22fb510b344b9d8971bb495126fe2ad413b4e91.png
6254 ms
sprites-s03cbf15c65-890feba8f6c6a12d6ded87c0e3fc130c56334bba958b2d0f35061421a510a170.png
6254 ms
real_time_updates-b57366538ec478bb86026d977becd769f951b06be5be02de7d3ce7b128f53eff.png
6254 ms
reports_all_kinds-3628190a41bfe4b5c9090a0bbd184f9cec097aa47ba832befd1cee2fd0ba4586.png
6583 ms
map_editing-7df15c15f330a3b3dae4cd8978355ef4e77b1e6dc716cfc0c9f98b0f86f718db.png
6582 ms
social-fcb986640b0a07c5c197041b958d88a036ba1ff3c917998bd9ba3039f3eccec6.png
6665 ms
fuel-806d1ba391833128050d8d9aed37a91761221e9d9c8afec10e4f7e11674b5814.png
6557 ms
footer-logo@2x-fd8d09a643d564a384f968f3e961e9a06374060146b0f5c6b532f8df3cd25755.png
6406 ms
country_by_ip
1912 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
2488 ms
DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff
2489 ms
MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff
3404 ms
k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff
3518 ms
fontawesome-webfont-ba0c59deb5450f5cb41b3f93609ee2d0d995415877ddfa223e8a8a7533474f07.woff
1700 ms
fontawesome-webfont.woff
1700 ms
get
1726 ms
collect
642 ms
collect
2200 ms
fontawesome-webfont.ttf
99 ms
fontawesome-webfont.svg
79 ms
waze.com accessibility score
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
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
waze.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
waze.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
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.
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: