4.9 sec in total
357 ms
4.4 sec
189 ms
Visit i2s.pt now to see the best up-to-date I 2 S content for Portugal and also check out these interesting facts you probably never knew about i2s.pt
A comprehensive solution to meet all the needs of the insurance market
Visit i2s.ptWe analyzed I2s.pt page load time and found that the first response time was 357 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
i2s.pt performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value11.9 s
0/100
25%
Value12.4 s
3/100
10%
Value290 ms
80/100
30%
Value0.756
6/100
15%
Value12.0 s
16/100
10%
357 ms
1476 ms
229 ms
663 ms
234 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 95% of them (37 requests) were addressed to the original I2s.pt, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain I2s.pt.
Page size can be reduced by 242.9 kB (18%)
1.3 MB
1.1 MB
In fact, the total size of I2s.pt 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. 20% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 8.3 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 3.6 kB, which is 33% 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 8.3 kB or 77% of the original size.
Potential reduce by 10.4 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. I 2 S images are well optimized though.
Potential reduce by 136.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 136.1 kB or 66% of the original size.
Potential reduce by 88.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. I2s.pt needs all CSS files to be minified and compressed as it can save up to 88.0 kB or 87% of the original size.
Number of requests can be reduced by 18 (64%)
28
10
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I 2 S. 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 7 to 1 for CSS and as a result speed up the page load time.
i2s.pt
357 ms
1476 ms
reset.css
229 ms
modernizr-2.0.6.js
663 ms
vag-rounded.css
234 ms
base.css
232 ms
layout.css
482 ms
print.css
240 ms
jquery-1.8.2.min.js
805 ms
jquery.validate.min.js
556 ms
messages_pt_PT.js
355 ms
base.js
362 ms
datepicker.min.css
488 ms
datepicker3.min.css
488 ms
bootstrap-datepicker.min.js
723 ms
home.js
603 ms
ga.js
45 ms
1051_1907x439.png
1797 ms
logo.png
133 ms
lang-menu-globe.png
123 ms
lang-menu-arrow.png
111 ms
auth-access.png
130 ms
news-list-small.png
123 ms
arrow.png
132 ms
pagination.png
225 ms
apcer.jpg
233 ms
footer.png
236 ms
1187_292x164.png
979 ms
1163_292x164.png
737 ms
1129_292x164.png
957 ms
vagroundedstd_bold-webfont.woff
254 ms
vagroundedstd_light-webfont.woff
255 ms
vagroundedstd_thin-webfont.woff
248 ms
vagroundedstd_black-webfont.woff
333 ms
__utm.gif
16 ms
vagroundedstd_bold-webfont.ttf
287 ms
vagroundedstd_light-webfont.ttf
131 ms
vagroundedstd_thin-webfont.ttf
256 ms
vagroundedstd_black-webfont.ttf
239 ms
i2s.pt accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
i2s.pt 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
i2s.pt 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I2s.pt can be misinterpreted by Google and other search engines. Our service has detected that English 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 I2s.pt 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.
i2s.pt
Open Graph data is detected on the main page of I 2 S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: