Tools & Wizards About Us

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

nexi.it

Nexi, l’innovazione dei pagamenti digitali in Italia

Page Load Speed

4.7 sec in total

First Response

590 ms

Resources Loaded

3.8 sec

Page Rendered

248 ms

About Website

Click here to check amazing Nexi content for Italy. Otherwise, check out these important facts you probably never knew about nexi.it

Nexi è la PayTech che costruisce il futuro dei pagamenti digitali in Italia, insieme alle sue Banche Partner, con soluzioni innovative per Privati e Aziende.

Visit nexi.it

Key Findings

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

Performance Metrics

nexi.it performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value2,900 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.545

13/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

www.nexi.it

590 ms

it

669 ms

gtm.js

101 ms

evergage.min.js

37 ms

clientlib-site.min.css

1273 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 50% of them (12 requests) were addressed to the original Nexi.it, 25% (6 requests) were made to Unpkg.com and 8% (2 requests) were made to Sdk.privacy-center.org. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Nexi.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 429.8 kB (55%)

Content Size

776.5 kB

After Optimization

346.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Nexi.it main page is 776.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. 20% of websites need less resources to load. CSS take 346.4 kB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 134.2 kB

  • Original 143.3 kB
  • After minification 72.8 kB
  • After compression 9.1 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 70.5 kB, which is 49% 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 134.2 kB or 94% of the original size.

JavaScript Optimization

-0%

Potential reduce by 24 B

  • Original 286.9 kB
  • After minification 286.9 kB
  • After compression 286.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.

CSS Optimization

-85%

Potential reduce by 295.6 kB

  • Original 346.4 kB
  • After minification 344.6 kB
  • After compression 50.8 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. Nexi.it needs all CSS files to be minified and compressed as it can save up to 295.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (73%)

Requests Now

15

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

nexi.it accessibility score

98

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

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

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

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