3.6 sec in total
906 ms
2.6 sec
98 ms
Welcome to pack.com.br homepage info - get ready to check Pack best content for Brazil right away, or after learning these important things about pack.com.br
Revista fisica e digital, há 40 anos no mercado, segmentada para o mercado de Embalagem.
Visit pack.com.brWe analyzed Pack.com.br page load time and found that the first response time was 906 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
pack.com.br performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value7.3 s
5/100
25%
Value8.3 s
19/100
10%
Value2,500 ms
4/100
30%
Value0.047
99/100
15%
Value23.9 s
1/100
10%
906 ms
415 ms
283 ms
293 ms
438 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 76% of them (39 requests) were addressed to the original Pack.com.br, 6% (3 requests) were made to E.issuu.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Pack.com.br.
Page size can be reduced by 185.2 kB (35%)
536.0 kB
350.9 kB
In fact, the total size of Pack.com.br main page is 536.0 kB. 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 285.2 kB which makes up the majority of the site volume.
Potential reduce by 24.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 17% 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 24.0 kB or 77% of the original size.
Potential reduce by 16.9 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. Pack images are well optimized though.
Potential reduce by 107.3 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 107.3 kB or 62% of the original size.
Potential reduce by 37.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. Pack.com.br needs all CSS files to be minified and compressed as it can save up to 37.0 kB or 81% of the original size.
Number of requests can be reduced by 28 (61%)
46
18
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pack. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pack.com.br
906 ms
ieindex.css
415 ms
iedivulgue_sua_empresa.css
283 ms
iecadastre_se.css
293 ms
iemaster.css
438 ms
ieminha_empresa.css
421 ms
urchin.js
6 ms
AC_RunActiveContent.js
428 ms
WebResource.axd
430 ms
ScriptResource.axd
455 ms
ScriptResource.axd
1033 ms
ScriptResource.axd
605 ms
embed.js
27 ms
tabs.css
155 ms
__utm.gif
10 ms
bg_alto_pattern.gif
138 ms
logo.gif
145 ms
setinha.jpg
141 ms
logo_pack.gif
174 ms
mini_logo_banas.gif
483 ms
mini_logo_ps.gif
548 ms
logo-guru.jpg
308 ms
banner_pack_portal.gif
705 ms
blog-pack.jpg
613 ms
banas-informa.jpg
802 ms
seta_dir_dupla.gif
798 ms
continuacao_detalhe_footer.gif
200 ms
bg_alto_curva.gif
200 ms
botao_vermelho.gif
195 ms
menu_bg_primeiro.jpg
324 ms
menu_bg_meio.jpg
264 ms
menu_bg_ultimo.jpg
362 ms
digital_pages.gif
349 ms
seta_azul.gif
346 ms
borda_pattern.gif
345 ms
bg_193.gif
405 ms
seta_laranja_semcorpo.gif
435 ms
bg_223.gif
476 ms
bot_esq.gif
477 ms
bot_dir.gif
480 ms
bg_424.gif
502 ms
bg_rodape_curva1.gif
768 ms
33187363.json
26 ms
embed-runner.js
29 ms
page_1.jpg
170 ms
quant.js
118 ms
css
78 ms
document.xml
64 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
35 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
38 ms
pixel;r=1513068795;a=p-5cvC4NOeGmtNA;fpan=1;fpa=P0-407081348-1458464941156;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458464941156;tzo=-180;ref=http%3A%2F%2Fpack.com.br%2F;url=about%3Ablank;ogl=
6 ms
pack.com.br accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
pack.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
pack.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Pack.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 Pack.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.
pack.com.br
Open Graph description is not detected on the main page of Pack. 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: