5.5 sec in total
548 ms
4.4 sec
567 ms
Visit igeoe.pt now to see the best up-to-date Igeoe content for Portugal and also check out these interesting facts you probably never knew about igeoe.pt
Fornecemos informação geográfica atualizada e pormenorizada direcionadas a geógrafos, escolas, câmaras, topógrafos, entre outros. Contacto: 218 505 368.
Visit igeoe.ptWe analyzed Igeoe.pt page load time and found that the first response time was 548 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
igeoe.pt performance score
548 ms
871 ms
278 ms
649 ms
381 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that all of those requests were addressed to Igeoe.pt and no external sources were called. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Igeoe.pt.
Page size can be reduced by 150.9 kB (11%)
1.4 MB
1.2 MB
In fact, the total size of Igeoe.pt main page is 1.4 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 38.1 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.9 kB, which is 26% 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 38.1 kB or 83% of the original size.
Potential reduce by 77.2 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. Igeoe images are well optimized though.
Potential reduce by 19.0 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 19.0 kB or 34% of the original size.
Potential reduce by 16.6 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. Igeoe.pt needs all CSS files to be minified and compressed as it can save up to 16.6 kB or 57% of the original size.
Number of requests can be reduced by 24 (33%)
72
48
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Igeoe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
igeoe.pt
548 ms
index.php
871 ms
site.css
278 ms
jquery-1.6.4.min.js
649 ms
site.js
381 ms
FakeElements.js
379 ms
jqContentSlider.js
402 ms
datafuncs.php
409 ms
jqImageCarousel.js
396 ms
_bg.jpg
554 ms
sombra.png
152 ms
logo1.jpg
214 ms
logo2.jpg
317 ms
img3.jpg
199 ms
img1.jpg
203 ms
img4.jpg
207 ms
pt.jpg
292 ms
img5.jpg
298 ms
img6.jpg
299 ms
img2_2.png
398 ms
JPG_58785c22c09bcdfd5a98b4c0d727182d.jpg
524 ms
JPG_69c82f8a5dca9edfc7069af0db9e42c7.jpg
515 ms
JPG_6bf5821e549b48aae0cfc3dc78618ced.jpg
620 ms
JPG_08f0ed863c7d0ff27e9196117037e8d5.jpg
536 ms
JPG_ed3c9bc7b9bbf71210193a2b5443bdfd.jpg
716 ms
JPG_c13caa11cdb732cf8bdbc4fc3e708a67.jpg
353 ms
JPG_8d0f9bcaf71f1ebf45bd43f8e9696dcd.jpg
475 ms
JPG_4a9f8c127fe6432510bca18197f8daf0.jpg
598 ms
JPG_f397aa6d9b336a5aae467bbe743f31e5.jpg
612 ms
JPG_76f2cf72a14497378599b9bbf75fdb25.jpg
625 ms
JPG_697537d5554c83bd39e9d4d626757e23.jpg
653 ms
JPG_4356d760eb7607979d53e87666270655.jpg
714 ms
JPG_7cbf200cdcb1d3231238e607a1451031.jpg
724 ms
JPG_ab1cedb2eac0c7fbd46cf96b39a0493e.jpg
721 ms
JPG_5fcd7159dabbb8cd43bc293a3633cb03.jpg
732 ms
JPG_751a885480e148f52dc29436bf041258.jpg
768 ms
JPG_2ac4a7f013f405d36877076908236d1f.jpg
827 ms
JPG_4db11c2a7598a6b28b05085690918163.jpg
823 ms
JPG_8d4cb6121eeaf6598c2e3777a20b712a.jpg
830 ms
JPG_fd9b48fdefdd998017659e9ee45a6f2d.jpg
824 ms
JPG_18364ec4511b2dc37f8fc5bc8047d8d6.jpg
836 ms
JPG_4a5acba7662f1fad6d716246b130bb4f.jpg
882 ms
JPG_fac1a2332d8dfea2eee0109e8b85b783.jpg
935 ms
JPG_93788452230592a4ea5f23cd4058d023.jpg
923 ms
JPG_d956245140a6c68cf1510048832def32.jpg
927 ms
JPG_28eae1f6df6d559fc827a8e13c9c8703.jpg
918 ms
JPG_9182ddd30c163b4cca126e6b347fad29.jpg
914 ms
JPG_4b1ff147296a89a881e14ea789e8359e.jpg
969 ms
JPG_871c553812ef1c7cab0c9c4b603a0593.jpg
1003 ms
JPG_bde9b7de81dbc5cf79cf9cbb3f4d5245.jpg
992 ms
JPG_658e560b6596b63884f1c0044b209997.jpg
927 ms
JPG_2427421b712ed7492168770251c848f4.jpg
926 ms
JPG_b35c1b0421777629b4a5958d7afa1995.jpg
937 ms
JPG_b67974513e3c6a401dc7fd843bf688f5.jpg
898 ms
img34.jpg
923 ms
img46.png
905 ms
blue_point.png
884 ms
none
763 ms
img35.png
739 ms
img37.png
811 ms
img39.jpg
817 ms
img20.jpg
772 ms
img40.jpg
758 ms
img42.jpg
756 ms
img43.jpg
742 ms
img47.jpg
784 ms
img45.jpg
754 ms
img23.jpg
791 ms
img25.jpg
753 ms
img24.jpg
753 ms
img41.jpg
742 ms
img21.jpg
784 ms
img10.jpg
740 ms
img11.png
764 ms
img22.jpg
753 ms
igeoe.pt SEO score
N/A
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igeoe.pt can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Igeoe.pt main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
igeoe.pt
Open Graph description is not detected on the main page of Igeoe. 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: