3.2 sec in total
325 ms
2.5 sec
350 ms
Welcome to codigo-postal.com.pt homepage info - get ready to check Codigo Postal best content for Portugal right away, or after learning these important things about codigo-postal.com.pt
o código Postal fornece todas as informações sobre as ruas de portugal
Visit codigo-postal.com.ptWe analyzed Codigo-postal.com.pt page load time and found that the first response time was 325 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
codigo-postal.com.pt performance score
325 ms
100 ms
187 ms
284 ms
195 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 42% of them (23 requests) were addressed to the original Codigo-postal.com.pt, 27% (15 requests) were made to Scontent.xx.fbcdn.net and 18% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (533 ms) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 205.6 kB (56%)
364.9 kB
159.3 kB
In fact, the total size of Codigo-postal.com.pt main page is 364.9 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. Javascripts take 126.7 kB which makes up the majority of the site volume.
Potential reduce by 72.7 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 10.1 kB, which is 12% 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 72.7 kB or 87% of the original size.
Potential reduce by 27.8 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. Obviously, Codigo Postal needs image optimization as it can save up to 27.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 71.7 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 71.7 kB or 57% of the original size.
Potential reduce by 33.5 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. Codigo-postal.com.pt needs all CSS files to be minified and compressed as it can save up to 33.5 kB or 86% of the original size.
Number of requests can be reduced by 25 (47%)
53
28
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Codigo Postal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.codigo-postal.com.pt
325 ms
style-Blue.css
100 ms
lightbox.css
187 ms
jquery.js
284 ms
lightbox.js
195 ms
brand
27 ms
superfish.js
196 ms
hoverIntent.js
193 ms
idtabs.js
194 ms
brand
38 ms
popreset.css
94 ms
ga.js
40 ms
bg.jpg
191 ms
logoBlue.png
123 ms
nav-bg.gif
119 ms
dropdown-bottom.png
119 ms
content-bg.gif
121 ms
bullet.gif
120 ms
google_custom_search_watermark.gif
99 ms
__utm.gif
55 ms
h3-bg.gif
123 ms
footer.gif
414 ms
bg-trans.png
100 ms
likebox.php
209 ms
likebox.php
237 ms
410ucuAGgaJ.css
179 ms
tSbl8xBI27R.css
222 ms
q68gy-v_YMF.js
305 ms
FJmpeSpHpjS.js
378 ms
0wM5s1Khldu.js
300 ms
1bNoFZUdlYZ.js
304 ms
307056_165130790239419_484400234_n.jpg
240 ms
12234943_905404989548716_1416240846219673099_n.jpg
315 ms
11148792_192952427708149_7572390584650450165_n.jpg
387 ms
12308811_10206313826057918_9110900394541773038_n.jpg
511 ms
12647430_1316268818399445_4256454279407848813_n.jpg
388 ms
12742704_10205469677132401_5753340702098963348_n.jpg
354 ms
12744213_10204804353023683_305541318143280890_n.jpg
400 ms
10354686_10150004552801856_220367501106153455_n.jpg
355 ms
12803008_10153543739689053_2820090639902558728_n.jpg
433 ms
1231095_500252410069117_779055667_n.jpg
428 ms
11205519_1054238044591966_1289218257884129344_n.jpg
472 ms
12715543_10207608361302588_5948158441596829877_n.jpg
474 ms
12631347_1007329169310743_5785094289749507914_n.jpg
499 ms
20256_104161422940579_6999932_n.jpg
533 ms
11074261_675924592514179_3802421500457277774_n.jpg
472 ms
wL6VQj7Ab77.png
74 ms
s7jcwEQH7Sx.png
73 ms
lightbox-close.png
97 ms
grey-panel-top.png
205 ms
grey-panel-middlex.png
99 ms
grey-panel-bottom.png
192 ms
lightbox-secure.png
100 ms
I6-MnjEovm5.js
45 ms
pQrUxxo5oQp.js
43 ms
codigo-postal.com.pt SEO score
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Codigo-postal.com.pt 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 Codigo-postal.com.pt 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.
codigo-postal.com.pt
Open Graph description is not detected on the main page of Codigo Postal. 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: