2.7 sec in total
86 ms
2.3 sec
288 ms
Welcome to metlife.es homepage info - get ready to check METLIFE best content for Italy right away, or after learning these important things about metlife.es
Seguros de Vida y Accidentes. Nuestros seguros de vida y accidentes cuidan de ti y de los tuyos. Se adaptan a tus necesidades para que vivas tranquilo.
Visit metlife.esWe analyzed Metlife.es page load time and found that the first response time was 86 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
metlife.es performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value7.6 s
3/100
25%
Value8.8 s
15/100
10%
Value4,830 ms
0/100
30%
Value0.15
76/100
15%
Value21.5 s
1/100
10%
86 ms
54 ms
54 ms
8 ms
32 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 86% of them (79 requests) were addressed to the original Metlife.es, 4% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (632 ms) belongs to the original domain Metlife.es.
Page size can be reduced by 285.1 kB (17%)
1.7 MB
1.4 MB
In fact, the total size of Metlife.es main page is 1.7 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. Only a small number of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 252.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. This page needs HTML code to be minified as it can gain 67.9 kB, which is 24% 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 252.9 kB or 90% of the original size.
Potential reduce by 31.9 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. METLIFE images are well optimized though.
Potential reduce by 50 B
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.
Potential reduce by 296 B
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. Metlife.es needs all CSS files to be minified and compressed as it can save up to 296 B or 20% of the original size.
Number of requests can be reduced by 38 (44%)
86
48
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of METLIFE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
metlife.es
86 ms
www.metlife.es
54 ms
css
54 ms
global.min.css
8 ms
site-vendor.min.css
32 ms
site-global.min.css
26 ms
site-component.min.css
69 ms
osano.js
478 ms
launch-7339c71fade7.min.js
47 ms
js
107 ms
iframeResizer.min.js
32 ms
formapp.min.css
38 ms
formapp.min.js
43 ms
site-vendor.min.js
42 ms
site-global.min.js
41 ms
site-component.min.js
45 ms
content-banner-dual-image-fix.css
65 ms
gtm.js
105 ms
icons-metlife.svg
80 ms
MetLife.png
78 ms
ico_life_insurance.png
72 ms
Pictogram_House_01.M.png
70 ms
Pictogram_Tooth_01.M.png
73 ms
ico_health.png
72 ms
ico_financial_reports.png
71 ms
ico_about_us.png
74 ms
ico_governance.png
72 ms
Pictogram_Building_02.M.png
74 ms
ico_newsroom.png
78 ms
ico_career.png
74 ms
ico_future.png
77 ms
ico_contact-us.png
74 ms
ico_file-a-claim.png
76 ms
ico_faq.png
75 ms
ico_glossary.png
77 ms
ico_forms-library.png
77 ms
carousel-stop.png
78 ms
carousel-play.png
79 ms
carousel-on.png
80 ms
carousel-off.png
78 ms
slider-home-1.jpg
83 ms
slider-home-2.jpg
80 ms
slider-home-3.jpg
82 ms
slider-MyMetLifeES-opt.jpg
81 ms
icon_getting_married.png
79 ms
icon_family.png
86 ms
icon_travel.png
84 ms
icon_future.png
82 ms
seguros-de-vida.jpg
84 ms
seguros-de-accidentes.jpg
86 ms
por-que-metlife.jpg
85 ms
1659529485615.jpg
88 ms
transparent-img.png
86 ms
0.gif
87 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A99d41P6zUNb.ttf
51 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBN9d41P6zUNb.ttf
54 ms
aemform.iframe.html
17 ms
iframeContentResizer.min.css
21 ms
iframeContentResizer.min.js
22 ms
core.min.css
18 ms
en.min.js
22 ms
main.min.js
19 ms
guideRuntime.min.css
21 ms
csrf.min.js
46 ms
csrf.min.js
288 ms
guideChartReducer.min.js
48 ms
guideRuntime.min.js
295 ms
widgets.min.css
47 ms
widgets.min.js
294 ms
timebased.min.js
289 ms
noConflict.min.js
288 ms
contentpage.min.css
290 ms
common.min.css
288 ms
common.min.css
292 ms
common.min.css
289 ms
contact-form-card.min.css
289 ms
main.min.css
289 ms
country-selector-all-flags-24.png
281 ms
busy-state.gif
252 ms
token.json
251 ms
jcr:content
134 ms
life_stage_divider.png
632 ms
responsive.min.css
576 ms
basicTheme.min.css
579 ms
_jcr_content
580 ms
token.json
510 ms
analytics.js
217 ms
o-0kIpQlx3QUlC5A4PNr4C5OaxRsfNNlKbCePevHtVtX57DGjDU1QNAZ6VfYyWtZ7rE.ttf
267 ms
o-0kIpQlx3QUlC5A4PNr4C5OaxRsfNNlKbCePevHtVtX57DGjDU1QDce6VfYyWtZ7rE.ttf
256 ms
collect
13 ms
collect
23 ms
ga-audiences
28 ms
metlife.es 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 input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Links do not have a discernible 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.
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.
metlife.es 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metlife.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Metlife.es 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.
metlife.es
Open Graph data is detected on the main page of METLIFE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: