Access piaggio.at. Piaggio: Roller und urbane Mobilität. Offizielle Seite

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

piaggio.at

440 ms

527 ms

chunk-vendors.css

120 ms

wl-theme-piaggio.css

94 ms

polyfill.min.js

20278 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Piaggio.at, 29% (5 requests) were made to Piaggio.com and 12% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Polyfill.io.

Content Size

143.3 kB

After Optimization

45.3 kB

In fact, the total size of Piaggio.at main page is 143.3 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 122.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 97.9 kB

Original 122.3 kB
After minification 122.1 kB
After compression 24.3 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 97.9 kB or 80% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

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

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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/).

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 Piaggio.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 Piaggio.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

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: