Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

pirolab.it

Pirolab By Diego Valobra – Diego Valobra UI/developer since 2006

Page Load Speed

8 sec in total

First Response

344 ms

Resources Loaded

7.6 sec

Page Rendered

53 ms

pirolab.it screenshot

About Website

Click here to check amazing Pirolab content for Russia. Otherwise, check out these important facts you probably never knew about pirolab.it

Visit pirolab.it

Key Findings

We analyzed Pirolab.it page load time and found that the first response time was 344 ms and then it took 7.6 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

pirolab.it performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

pirolab.it

344 ms

www.pirolab.it

1570 ms

wp-emoji-release.min.js

339 ms

layerslider.css

381 ms

style.min.css

410 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 89% of them (47 requests) were addressed to the original Pirolab.it, 9% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Pirolab.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.7 kB (7%)

Content Size

1.3 MB

After Optimization

1.3 MB

In fact, the total size of Pirolab.it main page is 1.3 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 728.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 53.8 kB

  • Original 66.6 kB
  • After minification 66.6 kB
  • After compression 12.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 53.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 395.5 kB
  • After minification 395.5 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. Pirolab images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 22.8 kB

  • Original 728.1 kB
  • After minification 728.1 kB
  • After compression 705.3 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

-10%

Potential reduce by 16.1 kB

  • Original 159.5 kB
  • After minification 159.5 kB
  • After compression 143.4 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. Pirolab.it has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (53%)

Requests Now

45

After Optimization

21

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

Accessibility Review

pirolab.it accessibility score

95

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

Links do not have a discernible name

Best Practices

pirolab.it 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

Missing source maps for large first-party JavaScript

SEO Factors

pirolab.it SEO score

93

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

    EN

  • Language Claimed

    IT

  • Encoding

    UTF-8

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