1.6 sec in total
157 ms
1.2 sec
240 ms
Visit online.metlife.com now to see the best up-to-date Online Metlife content for United States and also check out these interesting facts you probably never knew about online.metlife.com
Visit online.metlife.comWe analyzed Online.metlife.com page load time and found that the first response time was 157 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
online.metlife.com performance score
157 ms
86 ms
21 ms
145 ms
35 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 95% of them (95 requests) were addressed to the original Online.metlife.com, 3% (3 requests) were made to Nexus.ensighten.com and 2% (2 requests) were made to Statse.webtrendslive.com. The less responsive or slowest element that took the longest time to load (512 ms) belongs to the original domain Online.metlife.com.
Page size can be reduced by 1.6 MB (74%)
2.1 MB
546.8 kB
In fact, the total size of Online.metlife.com main page is 2.1 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. 50% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 20.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 3.4 kB, which is 13% 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 20.1 kB or 78% of the original size.
Potential reduce by 4.0 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. Obviously, Online Metlife needs image optimization as it can save up to 4.0 kB or 68% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.2 MB
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 1.2 MB or 74% of the original size.
Potential reduce by 317.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. Online.metlife.com needs all CSS files to be minified and compressed as it can save up to 317.0 kB or 76% of the original size.
Number of requests can be reduced by 84 (93%)
90
6
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Online 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 61 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
online.metlife.com
157 ms
online.metlife.com
86 ms
home
21 ms
login
145 ms
Bootstrap.js
35 ms
phoenix.css
18 ms
homepage.css
66 ms
login.css
72 ms
grid.css
87 ms
config.js
96 ms
dojo.js
159 ms
claro.css
65 ms
baseline.css
45 ms
typography.css
46 ms
widgets.css
60 ms
components.css
62 ms
template.css
74 ms
owl.css
62 ms
claroGrid.css
74 ms
mediabox.css
76 ms
formButton.css
79 ms
formTextBox.css
79 ms
MyAccounts.css
88 ms
MyProfile.css
92 ms
CustSupport.css
95 ms
qlac.css
98 ms
Payment.css
100 ms
AddProduct.css
104 ms
TabMenus.css
109 ms
agreements.css
105 ms
epolicy.css
112 ms
serverComponent.php
18 ms
registration.css
103 ms
a60c48b4702f8cddca60e479b2bce965.js
16 ms
main.js
512 ms
loader.js
70 ms
cookie.js
67 ms
array.js
66 ms
parser.js
64 ms
hash.js
65 ms
Dialog.js
64 ms
iframe.js
65 ms
_WidgetBase.js
65 ms
url.js
66 ms
registry.js
65 ms
window.js
67 ms
wtid.js
67 ms
bg-chp-pg.png
49 ms
bg-nav-header.png
49 ms
metLife_logo.png
49 ms
new_Login_Hero.jpg
48 ms
new_Login_Hero_medium.jpg
48 ms
popupbg.png
53 ms
new_Login_Hero_Small.jpg
54 ms
409b4bec-c67e-4764-a141-054db8df81d2.woff
78 ms
3c514636-142f-43f9-983f-76110a86b424.woff
43 ms
disabled.js
25 ms
regexp.js
40 ms
url.js
39 ms
stamp.js
48 ms
i18n.js
52 ms
Moveable.js
52 ms
TimedMoveable.js
52 ms
focus.js
62 ms
manager.js
62 ms
_Widget.js
63 ms
_TemplatedMixin.js
63 ms
_CssStateMixin.js
66 ms
_FormMixin.js
79 ms
_DialogMixin.js
77 ms
DialogUnderlay.js
82 ms
ContentPane.js
83 ms
text.js
89 ms
main.js
128 ms
_base.js
127 ms
Stateful.js
128 ms
Destroyable.js
127 ms
dcs.gif
10 ms
common.js
74 ms
touch.js
95 ms
common.js
92 ms
Mover.js
95 ms
a11y.js
91 ms
_OnDijitClickMixin.js
87 ms
_FocusMixin.js
110 ms
uacss.js
106 ms
hccss.js
104 ms
string.js
103 ms
cache.js
105 ms
BackgroundIframe.js
99 ms
_Container.js
100 ms
_ContentPaneResizeMixin.js
101 ms
html.js
104 ms
loading.js
104 ms
pm.js
72 ms
a11yclick.js
62 ms
autoscroll.js
47 ms
hccss.js
48 ms
Viewport.js
25 ms
utils.js
33 ms
online.metlife.com SEO score
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Online.metlife.com 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 Online.metlife.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
online.metlife.com
Open Graph description is not detected on the main page of Online 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: