Tools & Wizards About Us
metlife.pt screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 0

    Best Practices

  • 91

    SEO

    Google-friendlier than
    70% of websites

metlife.pt

Seguros de Vida e Acidentes: METLIFE Seguros Vida Acidentes

Page Load Speed

1.9 sec in total

First Response

91 ms

Resources Loaded

1.3 sec

Page Rendered

505 ms

metlife.pt screenshot

About Website

Visit metlife.pt now to see the best up-to-date METLIFE content for Portugal and also check out these interesting facts you probably never knew about metlife.pt

Seguros de Vida e de Acidentes Pessoais. Os nossos seguros de vida e acidentes pessoais cuidam de si e dos seus. Adaptam-se às suas necessidades para que viva tranquilo.

Visit metlife.pt

Key Findings

We analyzed Metlife.pt page load time and found that the first response time was 91 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

metlife.pt performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value23.2 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value3,370 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

metlife.pt

91 ms

www.metlife.pt

64 ms

global.min.css

15 ms

global.min.css

27 ms

clientlib-jquery.min.js

33 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 94% of them (62 requests) were addressed to the original Metlife.pt, 3% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Cmp.osano.com. The less responsive or slowest element that took the longest time to load (525 ms) relates to the external source Cmp.osano.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 123.8 kB (13%)

Content Size

932.3 kB

After Optimization

808.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Metlife.pt main page is 932.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. 70% of websites need less resources to load. Images take 694.4 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 122.5 kB

  • Original 136.7 kB
  • After minification 88.5 kB
  • After compression 14.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 48.2 kB, which is 35% 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 122.5 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 694.4 kB
  • After minification 693.1 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.

JavaScript Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 35 (58%)

Requests Now

60

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 60 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 19 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

metlife.pt

metlife.pt

91 ms

www.metlife.pt

www.metlife.pt

64 ms

global.min.css

global.min.css

15 ms

global.min.css

global.min.css

27 ms

clientlib-jquery.min.js

clientlib-jquery.min.js

33 ms

global.min.js

global.min.js

38 ms

osano.js

osano.js

525 ms

launch-7339c71fade7.min.js

launch-7339c71fade7.min.js

55 ms

js

js

78 ms

content.min.css

content.min.css

32 ms

clientlibs-header.min.js

clientlibs-header.min.js

40 ms

clientlibs-header.min.css

clientlibs-header.min.css

39 ms

clientlibs-search.min.js

clientlibs-search.min.js

39 ms

clientlibs-search.min.css

clientlibs-search.min.css

40 ms

clientlib-dropdown.min.js

clientlib-dropdown.min.js

40 ms

clientlib-dropdown.min.css

clientlib-dropdown.min.css

41 ms

clientlibs-navigation.min.js

clientlibs-navigation.min.js

42 ms

clientlibs-navigation.min.css

clientlibs-navigation.min.css

42 ms

clientlibs.min.css

clientlibs.min.css

44 ms

global.min.js

global.min.js

44 ms

clientlibs.min.js

clientlibs.min.js

41 ms

clientlibs.min.css

clientlibs.min.css

45 ms

clientlibs.min.js

clientlibs.min.js

44 ms

clientlibs.min.css

clientlibs.min.css

47 ms

clientlibs.min.css

clientlibs.min.css

46 ms

clientlibs.min.js

clientlibs.min.js

48 ms

clientlibs.min.css

clientlibs.min.css

47 ms

clientlibs.min.js

clientlibs.min.js

48 ms

clientlibs.min.css

clientlibs.min.css

51 ms

clientlibs.min.css

clientlibs.min.css

50 ms

clientlibs.min.css

clientlibs.min.css

50 ms

clientlibs.min.js

clientlibs.min.js

49 ms

clientlibs.min.js

clientlibs.min.js

49 ms

clientlibs.min.css

clientlibs.min.css

53 ms

clientlibs.min.js

clientlibs.min.js

51 ms

clientlibs.min.css

clientlibs.min.css

50 ms

clientlibs.min.js

clientlibs.min.js

51 ms

clientlibs.min.css

clientlibs.min.css

51 ms

gtm.js

gtm.js

50 ms

MetLife.png

MetLife.png

19 ms

m_au_governance_120p.svg

m_au_governance_120p.svg

24 ms

hr_Garnishments_120p.svg

hr_Garnishments_120p.svg

20 ms

p_special-needs_120p.svg

p_special-needs_120p.svg

24 ms

support_contact-us_120p.svg

support_contact-us_120p.svg

20 ms

m_au_corporate-responsibility_120p.svg

m_au_corporate-responsibility_120p.svg

22 ms

hr_Diversity-Inclusion_120p.svg

hr_Diversity-Inclusion_120p.svg

28 ms

p_group-insurance_120p.svg

p_group-insurance_120p.svg

25 ms

p_travel_120p.svg

p_travel_120p.svg

26 ms

p_loan-protection_120p.svg

p_loan-protection_120p.svg

29 ms

p_unit-link-life_120p.svg

p_unit-link-life_120p.svg

30 ms

icons-metlife.svg

icons-metlife.svg

5 ms

sorting_Desktop_Pattern.svg

sorting_Desktop_Pattern.svg

28 ms

MetLifeCircular-Medium.woff

MetLifeCircular-Medium.woff

81 ms

MetLifeCircular-Normal.woff

MetLifeCircular-Normal.woff

22 ms

MetLifeCircular-Light.woff

MetLifeCircular-Light.woff

193 ms

MetLifeCircular-Bold.woff

MetLifeCircular-Bold.woff

76 ms

categoria-vida.jpg

categoria-vida.jpg

59 ms

categoria-saude.jpg

categoria-saude.jpg

57 ms

categoria-acidentes.jpg

categoria-acidentes.jpg

60 ms

categoria-individual.jpg

categoria-individual.jpg

59 ms

categoria-pagamentos.jpg

categoria-pagamentos.jpg

60 ms

categoria-employee-benefits.jpg

categoria-employee-benefits.jpg

60 ms

www.metlife.pt

www.metlife.pt

41 ms

quotation.svg

quotation.svg

41 ms

metlife-portugal-esq.jpg

metlife-portugal-esq.jpg

26 ms

metlife-portugal-dir.jpg

metlife-portugal-dir.jpg

27 ms

Accessibility Review

metlife.pt accessibility score

65

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

metlife.pt SEO score

91

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

Social Sharing Optimization

metlife.pt

Open Graph description is not detected on the main page of METLIFE. 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: