2.2 sec in total
485 ms
1.6 sec
119 ms
Visit elife.com.br now to see the best up-to-date Elife content for Brazil and also check out these interesting facts you probably never knew about elife.com.br
E.life é a líder em monitorização, análise da mídia gerada pelo consumidor e gestão de relacionamento em mídias sociais na América Latina e Portugal.
Visit elife.com.brWe analyzed Elife.com.br page load time and found that the first response time was 485 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
elife.com.br performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value5.3 s
21/100
25%
Value17.7 s
0/100
10%
Value350 ms
73/100
30%
Value0.009
100/100
15%
Value21.2 s
1/100
10%
485 ms
149 ms
147 ms
322 ms
13 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 54% of them (32 requests) were addressed to the original Elife.com.br, 22% (13 requests) were made to Apis.google.com and 7% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (823 ms) belongs to the original domain Elife.com.br.
Page size can be reduced by 528.9 kB (27%)
2.0 MB
1.4 MB
In fact, the total size of Elife.com.br main page is 2.0 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 62.2 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 11.4 kB, which is 15% 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 62.2 kB or 84% of the original size.
Potential reduce by 101.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. Elife images are well optimized though.
Potential reduce by 207.5 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 207.5 kB or 65% of the original size.
Potential reduce by 158.1 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. Elife.com.br needs all CSS files to be minified and compressed as it can save up to 158.1 kB or 86% of the original size.
Number of requests can be reduced by 17 (31%)
55
38
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
elife.com.br
485 ms
screen.css
149 ms
print.css
147 ms
scripts.js
322 ms
recaptcha_ajax.js
13 ms
reset.css
68 ms
bootstrap.min.css
145 ms
ga.js
19 ms
banner2.png
562 ms
thump2.png
445 ms
thump2.png
254 ms
site1.png
258 ms
site1.png
255 ms
221.png
495 ms
221.png
351 ms
ebook-mobilife-13.png
370 ms
ebook-mobilife-13.png
350 ms
thump2.png
508 ms
site1.png
491 ms
facebook1.png
536 ms
unnamed-5.jpg
491 ms
screen-shot-2015-12-21-at-4.12_.29-pm_.png
546 ms
screen-shot-2015-10-15-at-4.14_.17-pm_.png
545 ms
screen-shot-2015-03-05-at-5.58_.51-pm_1.png
633 ms
jairson-espanol-1.jpg
582 ms
consumertribes1.png
602 ms
twitter_logo.jpg
621 ms
globo-pb.jpg
621 ms
globo.jpg
621 ms
continente-pb.jpg
660 ms
continente.jpg
666 ms
outlet.jpg
823 ms
outlet.jpg
779 ms
aimgdestaquetopo22.jpg
687 ms
all.js
76 ms
platform.js
180 ms
widgets.js
124 ms
__utm.gif
78 ms
222 ms
xd_arbiter.php
42 ms
xd_arbiter.php
100 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
72 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
70 ms
fastbutton
141 ms
fastbutton
138 ms
fastbutton
134 ms
fastbutton
254 ms
fastbutton
251 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.pt.html
146 ms
postmessageRelay
189 ms
rs=AGLTcCMZnOZwP_q6pCwQUYCN0BCxu9nBPg
90 ms
cb=gapi.loaded_0
48 ms
cb=gapi.loaded_1
48 ms
3193398744-postmessagerelay.js
22 ms
rpc:shindig_random.js
32 ms
cb=gapi.loaded_0
5 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
32 ms
jot.html
2 ms
elife.com.br 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
Links do not have a discernible name
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.
elife.com.br 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
elife.com.br 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
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elife.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Elife.com.br 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.
elife.com.br
Open Graph description is not detected on the main page of Elife. 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: