Tools & Wizards About Us
zellini.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

zellini.org

Fabrizio Zellini

Page Load Speed

1.9 sec in total

First Response

257 ms

Resources Loaded

1.5 sec

Page Rendered

158 ms

zellini.org screenshot

About Website

Welcome to zellini.org homepage info - get ready to check Zellini best content for Italy right away, or after learning these important things about zellini.org

Il blog di Fabrizio Zellini.

Visit zellini.org

Key Findings

We analyzed Zellini.org page load time and found that the first response time was 257 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

zellini.org performance score

0

Network Requests Diagram

zellini.org

257 ms

fabrizio.zellini.org

819 ms

style.css

85 ms

prettify.css

166 ms

calendario.css

168 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Zellini.org, 72% (13 requests) were made to Fabrizio.zellini.org and 11% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (819 ms) relates to the external source Fabrizio.zellini.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.4 kB (48%)

Content Size

154.5 kB

After Optimization

81.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zellini.org main page is 154.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. 25% of websites need less resources to load. Javascripts take 71.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 18.4 kB

  • Original 25.2 kB
  • After minification 24.1 kB
  • After compression 6.9 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 18.4 kB or 73% of the original size.

Image Optimization

-4%

Potential reduce by 1.5 kB

  • Original 39.3 kB
  • After minification 37.8 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. Zellini images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 38.8 kB

  • Original 71.6 kB
  • After minification 71.6 kB
  • After compression 32.8 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 38.8 kB or 54% of the original size.

CSS Optimization

-81%

Potential reduce by 14.7 kB

  • Original 18.3 kB
  • After minification 11.1 kB
  • After compression 3.5 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. Zellini.org needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (63%)

Requests Now

16

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zellini.org

zellini.org

257 ms

fabrizio.zellini.org

fabrizio.zellini.org

819 ms

style.css

style.css

85 ms

prettify.css

prettify.css

166 ms

calendario.css

calendario.css

168 ms

prettify.js

prettify.js

169 ms

lang-css.js

lang-css.js

174 ms

lang-sql.js

lang-sql.js

174 ms

wp-geshi-highlight.css

wp-geshi-highlight.css

191 ms

wp-embed.min.js

wp-embed.min.js

265 ms

plusone.js

plusone.js

94 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

92 ms

ga.js

ga.js

30 ms

P1040023-e1423728514269-300x249.jpg

P1040023-e1423728514269-300x249.jpg

183 ms

level-shifter-300x132.jpg

level-shifter-300x132.jpg

181 ms

footer_black.gif

footer_black.gif

84 ms

__utm.gif

__utm.gif

17 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

102 ms

SEO Factors

zellini.org SEO score

0

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zellini.org can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Zellini.org 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

zellini.org

Open Graph description is not detected on the main page of Zellini. 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: