6.6 sec in total
2.3 sec
3.9 sec
337 ms
Click here to check amazing Lifelife content. Otherwise, check out these important facts you probably never knew about lifelife.com.br
Welcome back to Instagram. Sign in to check out what your friends, family & interests have been capturing & sharing around the world.
Visit lifelife.com.brWe analyzed Lifelife.com.br page load time and found that the first response time was 2.3 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
lifelife.com.br performance score
name
value
score
weighting
Value2.2 s
76/100
10%
Value11.5 s
0/100
25%
Value5.1 s
62/100
10%
Value900 ms
31/100
30%
Value0.001
100/100
15%
Value10.6 s
23/100
10%
2330 ms
421 ms
407 ms
409 ms
435 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 79% of them (27 requests) were addressed to the original Lifelife.com.br, 9% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Lifelife.com.br.
Page size can be reduced by 411.3 kB (32%)
1.3 MB
872.0 kB
In fact, the total size of Lifelife.com.br 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. 35% of websites need less resources to load. Images take 791.1 kB which makes up the majority of the site volume.
Potential reduce by 34.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. 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 34.3 kB or 77% of the original size.
Potential reduce by 37.2 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. Lifelife images are well optimized though.
Potential reduce by 140.0 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 140.0 kB or 67% of the original size.
Potential reduce by 199.8 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. Lifelife.com.br needs all CSS files to be minified and compressed as it can save up to 199.8 kB or 84% of the original size.
Number of requests can be reduced by 12 (41%)
29
17
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifelife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
lifelife.com.br
2330 ms
style.css
421 ms
icons.css
407 ms
slider.css
409 ms
skinblue.css
435 ms
responsive.css
432 ms
bootstrap.min.css
51 ms
jquery.min.js
81 ms
bootstrap.min.js
59 ms
css
57 ms
modernizr-latest.js
691 ms
common.js
595 ms
jquery.cslider.js
596 ms
jquery.cycle.js
625 ms
jquery.carouFredSel-6.0.3-packed.js
822 ms
1.png
379 ms
logo.png
350 ms
noise.png
351 ms
shfinal.png
358 ms
d1.png
1019 ms
slider3.png
903 ms
familia.png
1185 ms
sh.png
474 ms
separators.png
503 ms
carousel_arrows.png
547 ms
individual.jpg
648 ms
casal.jpg
676 ms
familia.jpg
717 ms
empresarial.jpg
820 ms
logo-footer.png
851 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff
24 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
24 ms
fontawesome-webfont.woff
989 ms
lifelife.com.br 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
button, link, and menuitem elements do not have accessible names.
[role]s are not contained by their required parent element
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.
lifelife.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
lifelife.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifelife.com.br 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 Lifelife.com.br main page’s claimed encoding is iso-8859-1. 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.
lifelife.com.br
Open Graph description is not detected on the main page of Lifelife. 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: