Tools & Wizards About Us
60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% 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

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app

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

Page Load Speed

6 sec in total

First Response

421 ms

Resources Loaded

5.3 sec

Page Rendered

215 ms

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app screenshot

About Website

Click here to check amazing 60 Acfdc 0 Ef 67 A 7 Bb 452 Cae 11 Quirky Jang 9864 Ac Netlify content for India. Otherwise, check out these important facts you probably never knew about 60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.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 60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app

Key Findings

We analyzed 60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app page load time and found that the first response time was 421 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value10,180 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app

421 ms

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app

1253 ms

css

273 ms

css

124 ms

stub.js

913 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 66% of them (46 requests) were addressed to the original 60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app, 10% (7 requests) were made to Youtube.com and 4% (3 requests) were made to Cdn.iubenda.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain 60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

699.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app main page is 1.7 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. 75% 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 910.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 729.2 kB

  • Original 910.0 kB
  • After minification 910.0 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.2 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 Acfdc 0 Ef 67 A 7 Bb 452 Cae 11 Quirky Jang 9864 Ac Netlify images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 6.9 kB

  • Original 31.5 kB
  • After minification 31.5 kB
  • After compression 24.6 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 6.9 kB or 22% 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. 60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.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 28 (46%)

Requests Now

61

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 60 Acfdc 0 Ef 67 A 7 Bb 452 Cae 11 Quirky Jang 9864 Ac 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 26 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app

421 ms

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app

1253 ms

css

css

273 ms

css

css

124 ms

stub.js

stub.js

913 ms

iubenda_cs.js

iubenda_cs.js

913 ms

polyfill-874d5a1a7fa0e608cb77.js

polyfill-874d5a1a7fa0e608cb77.js

221 ms

component---src-pages-index-js-8b585947395bdeb06ba7.js

component---src-pages-index-js-8b585947395bdeb06ba7.js

463 ms

363066f59059c6dc2e60f47a77e26e9384b9fbac-ff612ffcc3eb461b3219.js

363066f59059c6dc2e60f47a77e26e9384b9fbac-ff612ffcc3eb461b3219.js

460 ms

f922d258cfa15148c9b316139a2d88de556551f7-b05c270261458fe7f5fd.js

f922d258cfa15148c9b316139a2d88de556551f7-b05c270261458fe7f5fd.js

461 ms

fef5354271cbbd0462b8440a029561ce8f5fbf4a-39a802c067ec3d56b4f3.js

fef5354271cbbd0462b8440a029561ce8f5fbf4a-39a802c067ec3d56b4f3.js

432 ms

92ceab8aff08f20bd7e2516dd30f31c003358d41-7b050a2ba08fd069d61b.js

92ceab8aff08f20bd7e2516dd30f31c003358d41-7b050a2ba08fd069d61b.js

432 ms

commons-50603296cac58dda8b17.js

commons-50603296cac58dda8b17.js

432 ms

52066749-99cbe044ac7d08c30bbf.js

52066749-99cbe044ac7d08c30bbf.js

507 ms

a9a7754c-74d59103587cddc27ee6.js

a9a7754c-74d59103587cddc27ee6.js

508 ms

484bcb1e-962fbdfa2fe520a1e13c.js

484bcb1e-962fbdfa2fe520a1e13c.js

507 ms

cb1608f2-d71d4e72756240ee359a.js

cb1608f2-d71d4e72756240ee359a.js

506 ms

styles-29163f9dced6fe4a408a.js

styles-29163f9dced6fe4a408a.js

507 ms

app-ead62ac842eedaef10cc.js

app-ead62ac842eedaef10cc.js

506 ms

framework-1d2634fc208542deb3df.js

framework-1d2634fc208542deb3df.js

577 ms

webpack-runtime-b28067f928034ae821d5.js

webpack-runtime-b28067f928034ae821d5.js

697 ms

gtm.js

gtm.js

460 ms

KAohxeJ_2Lk

KAohxeJ_2Lk

533 ms

sign-lez--gray-0d1a6a89c4c57489c3076e1b8ddac048.svg

sign-lez--gray-0d1a6a89c4c57489c3076e1b8ddac048.svg

503 ms

sign-lez--blue-d2a7f164919c8d2eb7b96944bd333e66.svg

sign-lez--blue-d2a7f164919c8d2eb7b96944bd333e66.svg

496 ms

sign-fr--white-50615f5c00a9292cc9c09046e011699f.svg

sign-fr--white-50615f5c00a9292cc9c09046e011699f.svg

505 ms

sign-it--white-77ff641e1a1b5f8b0f8f24749ceaa96f.svg

sign-it--white-77ff641e1a1b5f8b0f8f24749ceaa96f.svg

499 ms

sign-nl--white-b5c9270ebd3a83724b6932a7a55198cc.svg

sign-nl--white-b5c9270ebd3a83724b6932a7a55198cc.svg

616 ms

sign-pt--white-0e0dcd0609c967bdee7eb6e837853fa6.svg

sign-pt--white-0e0dcd0609c967bdee7eb6e837853fa6.svg

612 ms

sign-es--white-aa3020b8124e4d3bf83a942330c4c5ee.svg

sign-es--white-aa3020b8124e4d3bf83a942330c4c5ee.svg

624 ms

sign-se--lez2--white-2bc75a597ee1a4d949626073d8d3fed9.svg

sign-se--lez2--white-2bc75a597ee1a4d949626073d8d3fed9.svg

619 ms

sign-gb--white-c0d87e11e81ef623c207a7a886cfd83e.svg

sign-gb--white-c0d87e11e81ef623c207a7a886cfd83e.svg

629 ms

bg-traffic-f6b2c8e02e65777557ff8b6375a8e140.jpg

bg-traffic-f6b2c8e02e65777557ff8b6375a8e140.jpg

579 ms

map_europe--west--blueblue-d7a4bfaf1076cd8d8b69a5805169ba14.svg

map_europe--west--blueblue-d7a4bfaf1076cd8d8b69a5805169ba14.svg

561 ms

PbytFmztEwbIoce9zqA.woff

PbytFmztEwbIoce9zqA.woff

145 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYw.woff

146 ms

vvwPIbmJleNpjYGKAAFYG7ICTgYGRiZGZkYWRlZGNkZ2Rg5GTLT2nsiDDEEIZsZfmZRqZujmDaDcDAxcI7WIOpS2gtCWUdgQAZkcSmQAAAAFblbO6AAA=

vvwPIbmJleNpjYGKAAFYG7ICTgYGRiZGZkYWRlZGNkZ2Rg5GTLT2nsiDDEEIZsZfmZRqZujmDaDcDAxcI7WIOpS2gtCWUdgQAZkcSmQAAAAFblbO6AAA=

6 ms

www-player.css

www-player.css

195 ms

www-embed-player.js

www-embed-player.js

519 ms

base.js

base.js

558 ms

fetch-polyfill.js

fetch-polyfill.js

191 ms

dbedf643.js

dbedf643.js

521 ms

analytics.js

analytics.js

509 ms

core-en.js

core-en.js

563 ms

app-data.json

app-data.json

417 ms

page-data.json

page-data.json

406 ms

collect

collect

453 ms

2.4.2.css

2.4.2.css

439 ms

1002581746.json

1002581746.json

555 ms

1102003123.json

1102003123.json

560 ms

333984007.json

333984007.json

560 ms

ad_status.js

ad_status.js

591 ms

id

id

451 ms

Create

Create

1253 ms

qoe

qoe

1159 ms

wjh_uz0vV4kvmBh32RTA-9oL3vnIf1WTq69pxsOy-vU.js

wjh_uz0vV4kvmBh32RTA-9oL3vnIf1WTq69pxsOy-vU.js

1101 ms

embed.js

embed.js

909 ms

umwelt_city_sign--trans.png

umwelt_city_sign--trans.png

841 ms

page-data.json

page-data.json

508 ms

page-data.json

page-data.json

500 ms

page-data.json

page-data.json

467 ms

page-data.json

page-data.json

470 ms

page-data.json

page-data.json

526 ms

howto-1.png

howto-1.png

144 ms

howto-2.png

howto-2.png

143 ms

howto-3.png

howto-3.png

142 ms

howto-4.png

howto-4.png

144 ms

lez.jpg

lez.jpg

178 ms

streetauto.png

streetauto.png

170 ms

component---src-pages-imprint-js-3182311b4c2a71b49021.js

component---src-pages-imprint-js-3182311b4c2a71b49021.js

66 ms

Accessibility Review

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.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

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.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

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.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 60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.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 60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.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

60acfdc0ef67a7bb452cae11--quirky-jang-9864ac.netlify.app

Open Graph description is not detected on the main page of 60 Acfdc 0 Ef 67 A 7 Bb 452 Cae 11 Quirky Jang 9864 Ac 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: