3.8 sec in total
45 ms
2.5 sec
1.2 sec
Welcome to lifezette.com homepage info - get ready to check Life Zette best content for United States right away, or after learning these important things about lifezette.com
LifeZette: Life. Explained. The wonder, complexity, frustration and joys of life in all its variety. This is media built for the way we live—on the move.
Visit lifezette.comWe analyzed Lifezette.com page load time and found that the first response time was 45 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lifezette.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value17.4 s
0/100
25%
Value19.3 s
0/100
10%
Value4,590 ms
0/100
30%
Value0.651
9/100
15%
Value38.8 s
0/100
10%
45 ms
68 ms
174 ms
51 ms
36 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 54% of them (62 requests) were addressed to the original Lifezette.com, 7% (8 requests) were made to Use.typekit.net and 4% (5 requests) were made to S.ntv.io. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Ntvassets-a.akamaihd.net.
Page size can be reduced by 2.2 MB (40%)
5.5 MB
3.3 MB
In fact, the total size of Lifezette.com main page is 5.5 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 79.0 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 79.0 kB or 79% of the original size.
Potential reduce by 328.6 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, Life Zette needs image optimization as it can save up to 328.6 kB or 11% 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.3 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.3 MB or 70% of the original size.
Potential reduce by 466.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. Lifezette.com needs all CSS files to be minified and compressed as it can save up to 466.0 kB or 85% of the original size.
Number of requests can be reduced by 57 (58%)
98
41
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life Zette. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
lifezette.com
45 ms
www.lifezette.com
68 ms
geo3vnj.js
174 ms
style.css
51 ms
orgSeries.css
36 ms
easy-modal-site.css
33 ms
foobox.min.css
36 ms
carousel.css
34 ms
lifezette-code-library-public.css
37 ms
lifezette-us-map-interactive-public.css
49 ms
lifezette-helper-public.css
34 ms
checkbox.min.css
127 ms
form.min.css
35 ms
jquery.js
43 ms
jquery-migrate.min.js
46 ms
carousel.js
55 ms
lifezette-code-library-public-min.js
66 ms
mailer.js
65 ms
vendor-b97c59b1.js
64 ms
main-eaebe42a.js
64 ms
jquery.gray.min.js
382 ms
foobox.min.js
64 ms
yieldbot.intent.js
61 ms
load.js
127 ms
EPd7yllQ.js
65 ms
core.min.js
57 ms
position.min.js
51 ms
jquery.transit.min.js
306 ms
easy-modal-site.js
48 ms
jquery.usmapinit-min.js
75 ms
wp-embed.min.js
54 ms
ajax-forms.min.js
53 ms
embed.js
26 ms
wp-emoji-release.min.js
80 ms
www.lifezette.com
30 ms
moth-min.js
138 ms
init
14 ms
analytics.js
99 ms
lifezette-logo.png
93 ms
LifeZetteAppBannerAd.jpg
90 ms
Carousel-585x440_00000-504.jpg
410 ms
Carousel-585x440_00000-508.jpg
308 ms
Carousel-585x440_00000-5.jpg
408 ms
Carousel-585x440_00000-463.jpg
304 ms
Carousel-585x440_00000-519.jpg
459 ms
Carousel-585x440_00000-509.jpg
300 ms
OneThird-Video-360x340_00000-17-1.jpg
460 ms
TUES-REVISED-ONETHIRD.jpg
408 ms
OneThird-360x210_00000-3.jpg
400 ms
OneThird-360x210_00000-549.jpg
484 ms
OneThird-360x210_00000-511.jpg
496 ms
primary-ad-360x340_00000_480-2.png
499 ms
OneThird-360x210_00000-499.jpg
495 ms
OneThird-360x210_00000-547.jpg
498 ms
TwoThirds-750x420_00000.jpg
681 ms
Grief-Widget.jpg
685 ms
Widget-Video-555x313_00000-8.jpg
685 ms
mobile-app-icon-footer.png
167 ms
apple.png
167 ms
google.png
164 ms
t
252 ms
fontawesome-webfont.woff
214 ms
hQcx-nqoSME1EhiCtySy6eNy3Accd7nAgTS-GcXZtRIffHzZggMdeMJ6Mk6f5gI.woff
211 ms
b4i5yyLdROVttYFIA2BpVjroKalhwl0x2iYdC-27RNtffHYRggMdeMJ6Mk6f5gI.woff
320 ms
Z4cQjcf1mHxAWGGg9iMChAz8YX3nnY8l-H7Dy2dUzkJffHORggMdeMJ6Mk6f5Mt.woff
410 ms
Mf2wLAPvTROLs-gwmFHD3o_59dfK2IXnpME5Jmn50twffH2RggMdeMJ6Mk6f5MS.woff
607 ms
TPiw2hT2mqh5LzuLcjfDWU3IZQjz_BIASwW1fXdT7z9ffHVRggMdeMJ6Mk6f5Mb.woff
611 ms
initialize
409 ms
collect
191 ms
Ears-279x440_00000-519.jpg
519 ms
Ears-279x440_00000-509.jpg
506 ms
Ears-279x440_00000-504.jpg
518 ms
Ears-279x440_00000-508.jpg
556 ms
Ears-279x440_00000-5.jpg
721 ms
Ears-279x440_00000-464.jpg
557 ms
ajax-loader.gif
117 ms
related_aanbevolen.js
198 ms
ping.js
198 ms
vast.js
249 ms
jwpsrv.js
479 ms
gapro.js
248 ms
sharing.js
280 ms
collect
445 ms
816C945BE75C4DBF8481F5B1DBF4FC4A.png
343 ms
VideoPlayIcon.svg
362 ms
moatad.js
145 ms
trk.gif
141 ms
player-skin.css
308 ms
video.min.js
308 ms
moatvideo.js
123 ms
log
360 ms
pixel.gif
245 ms
f6096659966e35adf9d7bb4a20f03cbb6acb17c6ebd3854900d33a6afaa1fa90.png
1110 ms
sharing-skin.css
49 ms
bounce
57 ms
816C945BE75C4DBF8481F5B1DBF4FC4A.png
58 ms
pixel.gif
26 ms
LDYqRJtq.xml
109 ms
o5fqlnme.xml
25 ms
font.ttf
44 ms
acfb99c8682c8d8e118c3d9948e7dcbe95e8fc22b8eed9cf4d31868c538d67a8.png
837 ms
Article-1140x420_00000-551.jpg
53 ms
YmaW717Ae1zBIZoCJ0FE9jkk7NEYXq7dPDujZw3e9GqffJzjMUMdeMJ6Mk6f5M6.woff
33 ms
ttj
12 ms
i.js
26 ms
3f97584de232ec84649698a2eb93c462cc594b92.2.js
26 ms
callback=_nw2e.closures.c0
464 ms
print.png
80 ms
getids
52 ms
trk.gif
43 ms
foobox.svg
39 ms
foobox.woff
42 ms
p.gif
148 ms
e
47 ms
lifezette.com 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
lifezette.com 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
Browser errors were logged to the console
Page has valid source maps
lifezette.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Lifezette.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 Lifezette.com 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.
lifezette.com
Open Graph description is not detected on the main page of Life Zette. 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: