Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

inpiu.net

inpiu': notizie, analisi e commenti immediati e autorevoli

Page Load Speed

7.4 sec in total

First Response

644 ms

Resources Loaded

6.2 sec

Page Rendered

556 ms

inpiu.net screenshot

About Website

Visit inpiu.net now to see the best up-to-date Inpiu content and also check out these interesting facts you probably never knew about inpiu.net

Inpiu'.net: la dimensione strategica delle notizie. Analisi e commenti immediati dai maggiori esperti di Politica, Economia, Esteri.

Visit inpiu.net

Key Findings

We analyzed Inpiu.net page load time and found that the first response time was 644 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

inpiu.net performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.41

24/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

inpiu.net

644 ms

www.inpiu.net

673 ms

stile.css

214 ms

jquery-1.8.2.js

322 ms

jquery.masonry.min.js

217 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 92% of them (126 requests) were addressed to the original Inpiu.net, 1% (2 requests) were made to Facebook.com and 1% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Inpiu.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 207.2 kB (81%)

Content Size

255.3 kB

After Optimization

48.1 kB

In fact, the total size of Inpiu.net main page is 255.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. 55% of websites need less resources to load. HTML takes 153.1 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 138.1 kB

  • Original 153.1 kB
  • After minification 118.8 kB
  • After compression 15.0 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. This page needs HTML code to be minified as it can gain 34.3 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 138.1 kB or 90% of the original size.

JavaScript Optimization

-58%

Potential reduce by 32.0 kB

  • Original 55.0 kB
  • After minification 55.0 kB
  • After compression 23.1 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 32.0 kB or 58% of the original size.

CSS Optimization

-79%

Potential reduce by 37.1 kB

  • Original 47.1 kB
  • After minification 41.4 kB
  • After compression 10.0 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. Inpiu.net needs all CSS files to be minified and compressed as it can save up to 37.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (28%)

Requests Now

133

After Optimization

96

The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inpiu. 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 11 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

inpiu.net accessibility score

76

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

inpiu.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inpiu.net SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inpiu.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Inpiu.net 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 Inpiu. 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: