5.1 sec in total
657 ms
2.4 sec
2.1 sec
Visit primogenito.com.br now to see the best up-to-date Primogenito content and also check out these interesting facts you probably never knew about primogenito.com.br
Visit primogenito.com.brWe analyzed Primogenito.com.br page load time and found that the first response time was 657 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
primogenito.com.br performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value4.7 s
33/100
25%
Value4.4 s
74/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value4.5 s
82/100
10%
657 ms
86 ms
220 ms
101 ms
23 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 78% of them (49 requests) were addressed to the original Primogenito.com.br, 6% (4 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (911 ms) belongs to the original domain Primogenito.com.br.
Page size can be reduced by 898.1 kB (15%)
5.9 MB
5.0 MB
In fact, the total size of Primogenito.com.br main page is 5.9 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 5.1 MB which makes up the majority of the site volume.
Potential reduce by 146.9 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 146.9 kB or 92% of the original size.
Potential reduce by 263.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. Primogenito images are well optimized though.
Potential reduce by 257.9 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 257.9 kB or 65% of the original size.
Potential reduce by 229.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. Primogenito.com.br needs all CSS files to be minified and compressed as it can save up to 229.8 kB or 83% of the original size.
Number of requests can be reduced by 22 (39%)
57
35
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Primogenito. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
657 ms
polls-css.css
86 ms
style.css
220 ms
blue.css
101 ms
css
23 ms
css
36 ms
shortcodes.css
191 ms
carousel.css
125 ms
jquery.js
266 ms
jquery-migrate.min.js
150 ms
jquery.nivo.slider.js
174 ms
jquery.cycle.all.min.js
240 ms
polls-js.js
77 ms
analytics.js
6 ms
collect
126 ms
bg_003.jpg
114 ms
wrapper.png
80 ms
bg.png
80 ms
IMG_2391.jpg
212 ms
IMG_2393.jpg
337 ms
IMG_2396.jpg
338 ms
IMG_2397.jpg
211 ms
IMG_2404.jpg
161 ms
IMG_2403.jpg
190 ms
facebook.png
211 ms
twitter.png
336 ms
pinterest.png
337 ms
plusone.png
340 ms
linkedin.png
340 ms
digg.png
341 ms
delicious.png
342 ms
reddit.png
344 ms
stumbleupon.png
342 ms
tumblr.png
344 ms
posterous.png
345 ms
email.png
347 ms
snailmail.png
347 ms
IMG_1869-0.jpg
911 ms
IMG_1936.jpg
833 ms
IMG_1856.jpg
813 ms
IMG_1855.jpg
784 ms
20140706-111432-40472174.jpg
377 ms
20140706-111435-40475065.jpg
422 ms
20140706-111431-40471898.jpg
466 ms
20140706-111433-40473742.jpg
508 ms
20140321-205654.jpg
552 ms
wpid-20131021_112004.jpg
609 ms
wpid-20130929_164653.jpg
615 ms
button.png
645 ms
isaac2.jpg
648 ms
2Q-AW1e_taO6pHwMXcXW5w.ttf
9 ms
IGQFaxr6QFntFZmYFeQEew.ttf
16 ms
QpebnqPZM6s
61 ms
sidebar_arrow.png
609 ms
loading.gif
645 ms
www-embed-player-vflfNyN_r.css
38 ms
www-embed-player.js
66 ms
base.js
89 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
64 ms
ad_status.js
73 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
44 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
47 ms
.png
492 ms
primogenito.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
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
primogenito.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
primogenito.com.br SEO score
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Primogenito.com.br 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 Primogenito.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.
primogenito.com.br
Open Graph description is not detected on the main page of Primogenito. 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: