Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app

DRIVE2.CITY: Low-emission zones in your navigation.

Page Load Speed

8.2 sec in total

First Response

489 ms

Resources Loaded

7.5 sec

Page Rendered

219 ms

60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app screenshot

About Website

Visit 60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app now to see the best up-to-date 60 Aac 19 F 06 D 03 C 0008 Fe 0 Da Vigilant Golick 237 57 Netlify content for India and also check out these interesting facts you probably never knew about 60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app

Online check of LEZ accessibility in EU cities. Get the directions that meet local access regulations. Explore the Park & Ride alternatives, stay mobile.

Visit 60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app

Key Findings

We analyzed 60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app page load time and found that the first response time was 489 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value4,470 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app

489 ms

60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app

1143 ms

css

226 ms

css

100 ms

stub.js

1758 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 64% of them (46 requests) were addressed to the original 60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app, 10% (7 requests) were made to Youtube.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Cdn.iubenda.com.

Page Optimization Overview & Recommendations

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

Content Size

1.8 MB

After Optimization

723.6 kB

In fact, the total size of 60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app main page is 1.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 909.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 729.0 kB

  • Original 909.8 kB
  • After minification 909.8 kB
  • After compression 180.8 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 729.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 2 B

  • Original 431.6 kB
  • After minification 431.6 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. 60 Aac 19 F 06 D 03 C 0008 Fe 0 Da Vigilant Golick 237 57 Netlify images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 45.6 kB

  • Original 94.5 kB
  • After minification 94.3 kB
  • After compression 48.9 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 45.6 kB or 48% of the original size.

CSS Optimization

-83%

Potential reduce by 311.1 kB

  • Original 373.4 kB
  • After minification 373.2 kB
  • After compression 62.3 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. 60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app needs all CSS files to be minified and compressed as it can save up to 311.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (46%)

Requests Now

63

After Optimization

34

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 60 Aac 19 F 06 D 03 C 0008 Fe 0 Da Vigilant Golick 237 57 Netlify. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app accessibility score

87

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app SEO score

85

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app 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 60aac19f06d03c0008fe0da0--vigilant-golick-237d57.netlify.app 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

Open Graph description is not detected on the main page of 60 Aac 19 F 06 D 03 C 0008 Fe 0 Da Vigilant Golick 237 57 Netlify. 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: