Tools & Wizards About Us
waze.co.il screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

waze.co.il

Driving directions, live traffic & road conditions updates - Waze

Page Load Speed

783 ms in total

First Response

77 ms

Resources Loaded

615 ms

Page Rendered

91 ms

waze.co.il screenshot

About Website

Welcome to waze.co.il homepage info - get ready to check Waze best content for Israel right away, or after learning these important things about waze.co.il

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

Visit waze.co.il

Key Findings

We analyzed Waze.co.il page load time and found that the first response time was 77 ms and then it took 706 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

waze.co.il performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

waze.co.il

77 ms

www.waze.com

73 ms

18 ms

218 ms

gtm.js

86 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Waze.co.il, 61% (11 requests) were made to Web-assets.waze.com and 17% (3 requests) were made to Waze.com. The less responsive or slowest element that took the longest time to load (218 ms) relates to the external source Waze.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 141.8 kB (14%)

Content Size

1.0 MB

After Optimization

878.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waze.co.il main page is 1.0 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. 45% of websites need less resources to load. Javascripts take 813.8 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 38.9 kB

  • Original 56.3 kB
  • After minification 56.2 kB
  • After compression 17.4 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 38.9 kB or 69% of the original size.

Image Optimization

-3%

Potential reduce by 16 B

  • Original 595 B
  • After minification 579 B

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

-0%

Potential reduce by 50 B

  • Original 813.8 kB
  • After minification 813.8 kB
  • After compression 813.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-69%

Potential reduce by 102.9 kB

  • Original 149.5 kB
  • After minification 148.9 kB
  • After compression 46.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.co.il needs all CSS files to be minified and compressed as it can save up to 102.9 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (64%)

Requests Now

14

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waze. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

waze.co.il

waze.co.il

77 ms

www.waze.com

www.waze.com

73 ms

18 ms

218 ms

gtm.js

gtm.js

86 ms

vendor-9efb63ad4c25c0339af2.css

vendor-9efb63ad4c25c0339af2.css

25 ms

waze-vendor-fa87319c3e7e8a7b0391.css

waze-vendor-fa87319c3e7e8a7b0391.css

28 ms

common-dd1f94ac416934d33120.css

common-dd1f94ac416934d33120.css

146 ms

livemap-270fb08a4780595435d0.css

livemap-270fb08a4780595435d0.css

34 ms

page-loader-background-234289043eec2b9063539bc7181c60ef.png

page-loader-background-234289043eec2b9063539bc7181c60ef.png

32 ms

css

css

29 ms

common-11163206dc04f00e97e5.js

common-11163206dc04f00e97e5.js

14 ms

vendor-c744df1bcd768966956d.js

vendor-c744df1bcd768966956d.js

26 ms

waze-vendor-eb4a5d71f1465f19aa88.js

waze-vendor-eb4a5d71f1465f19aa88.js

33 ms

livemap-2752d8ec44b2f2013b33.js

livemap-2752d8ec44b2f2013b33.js

21 ms

loader_white_bg@2x-e5fc188df87bbe7b6e3ef69aea522140.gif

loader_white_bg@2x-e5fc188df87bbe7b6e3ef69aea522140.gif

24 ms

map-placeholder-306089143fcd4e061cdb3b946ccec977.png

map-placeholder-306089143fcd4e061cdb3b946ccec977.png

31 ms

analytics.js

analytics.js

44 ms

Accessibility Review

waze.co.il 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.co.il best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

waze.co.il SEO score

92

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waze.co.il can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Waze.co.il 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.co.il

Open Graph data is detected on the main page of Waze. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: