3.1 sec in total
353 ms
2.6 sec
235 ms
Click here to check amazing EIZO content for Italy. Otherwise, check out these important facts you probably never knew about eizo.it
I monitor EIZO sono sinonimo di massima qualità. Ogni monitor EIZO è caratterizzato da un'eccezionale qualità d'immagine, ergonomia e durata.
Visit eizo.itWe analyzed Eizo.it page load time and found that the first response time was 353 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
eizo.it performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value7.0 s
6/100
25%
Value8.9 s
15/100
10%
Value7,930 ms
0/100
30%
Value0.544
13/100
15%
Value15.0 s
7/100
10%
353 ms
694 ms
30 ms
293 ms
50 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 89% of them (42 requests) were addressed to the original Eizo.it, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (867 ms) belongs to the original domain Eizo.it.
Page size can be reduced by 195.5 kB (25%)
787.4 kB
592.0 kB
In fact, the total size of Eizo.it main page is 787.4 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. 30% of websites need less resources to load. Images take 503.2 kB which makes up the majority of the site volume.
Potential reduce by 21.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 21.9 kB or 76% of the original size.
Potential reduce by 16.3 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. EIZO images are well optimized though.
Potential reduce by 106.5 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 106.5 kB or 54% of the original size.
Potential reduce by 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. Eizo.it needs all CSS files to be minified and compressed as it can save up to 50.8 kB or 87% of the original size.
Number of requests can be reduced by 14 (31%)
45
31
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EIZO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
eizo.it
353 ms
www.eizo.it
694 ms
ga.js
30 ms
merged-c03a5d37df6285e70f3b72653512bfff.css
293 ms
jquery.min.js
50 ms
merged-ee1fbc43d25dd59d41079c1b7108fee7.js
578 ms
jquery-ui.min.js
50 ms
__utm.gif
12 ms
merged-c1a9f6cbc42b31f76286d9c7e4985929.js
109 ms
bg_top_kachel.jpg
98 ms
px.png
577 ms
bg_top_all.png
293 ms
img_logo.jpg
100 ms
icon_naviarrow.gif
100 ms
bg_select.gif
102 ms
global.gif
197 ms
select_plus.gif
196 ms
bg_navMain.png
291 ms
nav_layer.gif
199 ms
NavLayer_FlexScan_EV.png
200 ms
NavLayer_ColorEdge.png
390 ms
NavLayer_FORIS.png
389 ms
NavLayer_RadiForce.png
295 ms
NavLayer_DuraVision.png
298 ms
NavLayer_Raptor.png
387 ms
NavLayer_Accessorie.png
386 ms
nav_layer_repeat.gif
392 ms
search.gif
393 ms
bg_slider.jpg
483 ms
fs2735_it.jpg
675 ms
bg_box677_home.jpg
486 ms
News_Wazer_IT.jpg
581 ms
btn_167px.jpg
488 ms
News_FS2735.png
586 ms
btn_116px.jpg
579 ms
News_FF.png
677 ms
bg_box274_home.jpg
584 ms
bgLink.gif
675 ms
Icon_WhitePaper.png
677 ms
Special_Microsites.png
685 ms
bg_specialbox979.jpg
684 ms
teaser_img_advisor.png
771 ms
btn_153px.jpg
772 ms
teaser_img_Wissenswertes_ColorEdge.png
867 ms
img_facebook.png
772 ms
arrow_select.gif
720 ms
print.css
98 ms
eizo.it accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eizo.it best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
eizo.it SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eizo.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 Eizo.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.
eizo.it
Open Graph description is not detected on the main page of EIZO. 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: