Tools & Wizards About Us
vespa.at screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

vespa.at

Vespa Piaggio, eine italienische Stil-Ikone seit 1946 | Vespa.com

Page Load Speed

2.5 sec in total

First Response

416 ms

Resources Loaded

1.8 sec

Page Rendered

274 ms

vespa.at screenshot

About Website

Click here to check amazing Vespa content for Austria. Otherwise, check out these important facts you probably never knew about vespa.at

Entdecken Sie auf Vespa.com alle Modelle, Aktionen und Neuigkeiten aus der Vespa-Welt, einer italienischen Stilikone in der Welt der Mobilität seit 1946.

Visit vespa.at

Key Findings

We analyzed Vespa.at page load time and found that the first response time was 416 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

vespa.at performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

8/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

vespa.at

416 ms

414 ms

chunk-vendors.css

157 ms

wl-theme-vespa.css

67 ms

polyfill.min.js

62 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 10% of them (1 request) were addressed to the original Vespa.at, 50% (5 requests) were made to Vespa.com and 10% (1 request) were made to Polyfill.io. The less responsive or slowest element that took the longest time to load (634 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.0 kB (69%)

Content Size

14.5 kB

After Optimization

4.5 kB

  • HTML

In fact, the total size of Vespa.at main page is 14.5 kB. 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. HTML takes 14.5 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.0 kB

  • Original 14.5 kB
  • After minification 14.3 kB
  • After compression 4.5 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.0 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

  • JavaScript
  • CSS

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

Network Requests Diagram

vespa.at

vespa.at

416 ms

414 ms

chunk-vendors.css

chunk-vendors.css

157 ms

wl-theme-vespa.css

wl-theme-vespa.css

67 ms

polyfill.min.js

polyfill.min.js

62 ms

chunk-vendors.js

chunk-vendors.js

156 ms

app.js

app.js

60 ms

css2

css2

106 ms

gtm.js

gtm.js

634 ms

7938M-VJ64B-QS6R3-C5LRD-8RQHC

7938M-VJ64B-QS6R3-C5LRD-8RQHC

530 ms

Accessibility Review

vespa.at accessibility score

89

Accessibility Issues

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

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

Best Practices

vespa.at best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

vespa.at SEO score

100

Search Engine Optimization Advices

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

    DE

  • Language Claimed

    DE

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vespa.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Vespa.at main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

vespa.at

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: