15.3 sec in total
1.9 sec
13.2 sec
263 ms
Welcome to pamplona.com.br homepage info - get ready to check Pamplona best content for Brazil right away, or after learning these important things about pamplona.com.br
O Pamplona Alimentos S/A, sociedade anônima de capital fechado, foi fundado em 03 de maio de 1948, pelo Sr. Lauro Pamplona e sua esposa Sra. Ana Pamplona.
Visit pamplona.com.brWe analyzed Pamplona.com.br page load time and found that the first response time was 1.9 sec and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pamplona.com.br performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value18.1 s
0/100
25%
Value6.2 s
43/100
10%
Value790 ms
37/100
30%
Value0.04
99/100
15%
Value13.0 s
13/100
10%
1913 ms
4619 ms
841 ms
648 ms
867 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 74% of them (127 requests) were addressed to the original Pamplona.com.br, 6% (11 requests) were made to Apis.google.com and 5% (8 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Pamplona.com.br.
Page size can be reduced by 1.1 MB (28%)
4.0 MB
2.9 MB
In fact, the total size of Pamplona.com.br main page is 4.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. 65% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 186.6 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 186.6 kB or 79% of the original size.
Potential reduce by 50.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. Pamplona images are well optimized though.
Potential reduce by 588.8 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 588.8 kB or 66% of the original size.
Potential reduce by 300.7 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. Pamplona.com.br needs all CSS files to be minified and compressed as it can save up to 300.7 kB or 84% of the original size.
Number of requests can be reduced by 38 (23%)
165
127
The browser has sent 165 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pamplona. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
pamplona.com.br
1913 ms
www.pamplona.com.br
4619 ms
normalize.css
841 ms
colorbox.css
648 ms
chosen.css
867 ms
960_24_col.css
663 ms
style.css
1396 ms
html5.js
646 ms
al-jquery.js
1594 ms
al-cycle2.js
1043 ms
al-mask.js
868 ms
al-validate.js
1089 ms
al-colorbox.js
1117 ms
arealocal.js
1178 ms
funcoes.js
1469 ms
validacoes.js
1313 ms
al-chosen.js
1357 ms
addthis_widget.js
11 ms
analytics.js
56 ms
fundo.jpg
264 ms
logo_2016.png
479 ms
flags.png
261 ms
ok.png
260 ms
fundo_submenu.png
262 ms
fundo-topo1.png
299 ms
banner-carne-suina2.jpg
1289 ms
Banner-presunto31.jpg
783 ms
Banner-salame3.jpg
993 ms
Banner-salame22.jpg
854 ms
Banner-presunto21.jpg
892 ms
setaBanner.png
692 ms
pontilhado.png
903 ms
timthumb.php
1085 ms
timthumb.php
1126 ms
timthumb.php
1699 ms
timthumb.php
1138 ms
timthumb.php
1270 ms
timthumb.php
1351 ms
timthumb.php
1757 ms
timthumb.php
1397 ms
timthumb.php
1520 ms
timthumb.php
1791 ms
timthumb.php
1631 ms
timthumb.php
1684 ms
timthumb.php
1759 ms
timthumb.php
1878 ms
timthumb.php
1935 ms
timthumb.php
1947 ms
timthumb.php
2026 ms
timthumb.php
1996 ms
timthumb.php
2047 ms
timthumb.php
2163 ms
timthumb.php
2174 ms
timthumb.php
2197 ms
timthumb.php
2198 ms
collect
64 ms
300lo.json
36 ms
all.js&version=v2.0
109 ms
widgets.js
32 ms
plusone.js
70 ms
collect
131 ms
Z3CSWzjw82Y
129 ms
sh.8e5f85691f9aaa082472a194.html
39 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
82 ms
cb=gapi.loaded_0
71 ms
cb=gapi.loaded_1
91 ms
fastbutton
141 ms
fastbutton
205 ms
fastbutton
213 ms
227 ms
www-embed-player-vflfNyN_r.css
103 ms
www-embed-player.js
118 ms
timthumb.php
2031 ms
timthumb.php
2035 ms
timthumb.php
2153 ms
xd_arbiter.php
58 ms
xd_arbiter.php
108 ms
timthumb.php
2131 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.pt.html
34 ms
postmessageRelay
120 ms
timthumb.php
2152 ms
rs=AGLTcCNM-48YL59d_yswpJ-6bM96iifCIg
9 ms
cb=gapi.loaded_0
62 ms
cb=gapi.loaded_1
69 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
116 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
62 ms
ad_status.js
80 ms
3193398744-postmessagerelay.js
48 ms
rpc:shindig_random.js
43 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
57 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
57 ms
cb=gapi.loaded_0
11 ms
timthumb.php
2022 ms
jot.html
2 ms
timthumb.php
1869 ms
timthumb.php
1764 ms
timthumb.php
1799 ms
timthumb.php
1778 ms
timthumb.php
1789 ms
timthumb.php
1757 ms
timthumb.php
1697 ms
timthumb.php
1699 ms
timthumb.php
1748 ms
timthumb.php
1671 ms
timthumb.php
1686 ms
timthumb.php
1645 ms
timthumb.php
1624 ms
timthumb.php
1632 ms
timthumb.php
1535 ms
timthumb.php
1508 ms
timthumb.php
1522 ms
timthumb.php
1510 ms
timthumb.php
1531 ms
timthumb.php
1655 ms
timthumb.php
1550 ms
timthumb.php
1549 ms
timthumb.php
1529 ms
timthumb.php
1512 ms
timthumb.php
1507 ms
timthumb.php
1615 ms
timthumb.php
1524 ms
timthumb.php
1542 ms
timthumb.php
1542 ms
timthumb.php
1539 ms
timthumb.php
1512 ms
timthumb.php
1639 ms
timthumb.php
1556 ms
timthumb.php
1576 ms
timthumb.php
1561 ms
timthumb.php
1537 ms
timthumb.php
1510 ms
timthumb.php
1625 ms
timthumb.php
1610 ms
timthumb.php
1611 ms
timthumb.php
1618 ms
timthumb.php
1584 ms
timthumb.php
1572 ms
timthumb.php
1618 ms
timthumb.php
1652 ms
timthumb.php
1624 ms
timthumb.php
1623 ms
timthumb.php
1650 ms
timthumb.php
1651 ms
timthumb.php
1586 ms
timthumb.php
1639 ms
timthumb.php
1618 ms
timthumb.php
1629 ms
timthumb.php
1637 ms
banner_calculadora_pt.jpg
1679 ms
like.php
115 ms
like.php
104 ms
like.php
118 ms
banner_receita_hover_pt.png
1552 ms
qeKvIRsJabD.js
45 ms
LVx-xkvaJ0b.png
29 ms
banner_receita_pt.jpg
1767 ms
banner_bndes_pt.gif
2122 ms
y.png
1739 ms
f.png
1710 ms
KIT_FESTA_2015_01.jpg
2255 ms
pontilhado_branco.png
1552 ms
sprite_footer.png
1781 ms
fundo-rodape.png
1785 ms
fundo-menu.png
1749 ms
sprite_scroll.png
1719 ms
scroll.png
1887 ms
overlay.png
1835 ms
ping
44 ms
like.php
70 ms
like.php
59 ms
like.php
56 ms
pamplona.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
pamplona.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
pamplona.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
Image elements do not have [alt] attributes
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pamplona.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 Pamplona.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.
pamplona.com.br
Open Graph description is not detected on the main page of Pamplona. 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: