8.9 sec in total
2.5 sec
5.9 sec
464 ms
Click here to check amazing Odivelas content for Portugal. Otherwise, check out these important facts you probably never knew about odivelas.com
Visit odivelas.comWe analyzed Odivelas.com page load time and found that the first response time was 2.5 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
odivelas.com performance score
2483 ms
114 ms
228 ms
1319 ms
225 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 76% of them (83 requests) were addressed to the original Odivelas.com, 7% (8 requests) were made to Apis.google.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Odivelas.com.
Page size can be reduced by 1.3 MB (36%)
3.5 MB
2.2 MB
In fact, the total size of Odivelas.com main page is 3.5 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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 68.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. 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 68.7 kB or 82% of the original size.
Potential reduce by 846.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. Obviously, Odivelas needs image optimization as it can save up to 846.6 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 260.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 260.7 kB or 68% of the original size.
Potential reduce by 105.1 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. Odivelas.com needs all CSS files to be minified and compressed as it can save up to 105.1 kB or 85% of the original size.
Number of requests can be reduced by 37 (36%)
103
66
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Odivelas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
odivelas.com
2483 ms
wp-emoji-release.min.js
114 ms
style.css
228 ms
css_options.php
1319 ms
prettyPhoto.css
225 ms
shortcodes.css
226 ms
shortcodes-blog.css
226 ms
slider.css
227 ms
feature.css
331 ms
slicknav.css
332 ms
respond.css
333 ms
css
29 ms
bbpress.css
335 ms
wpp.css
335 ms
style.css
442 ms
jquery.js
563 ms
jquery-migrate.min.js
446 ms
editor.js
446 ms
flexslider.js
447 ms
prettyPhoto.js
554 ms
backstretch.js
555 ms
ticker.js
556 ms
rotator.js
676 ms
idTabs.js
664 ms
slicknav.js
665 ms
modernizr.js
668 ms
script.js
670 ms
wp-embed.min.js
775 ms
ga.js
99 ms
logo.png
223 ms
banner_nos1.jpg
571 ms
background.png
224 ms
search-header.png
224 ms
breaking-news.png
221 ms
ReparacoesAgua6A.jpg
564 ms
PCesarTeixeira20160309-620x425.png
1168 ms
CACdaPontinha.jpeg
568 ms
JMP_650-620x425.png
1169 ms
OPredio-620x425.png
1153 ms
CAC-AG.jpg
712 ms
TERRACELL-logo.png
711 ms
jsd-odivelas-421x211.jpg
828 ms
osVerdes.jpg
841 ms
coracao_cmo-421x211.jpg
948 ms
CAC-Valongo4Fev2012.jpg
1040 ms
cmo2-294x211.jpg
1068 ms
HMartins20160223-421x211.png
1386 ms
JPedroGalhofo-421x211.png
1482 ms
ReparacoesAgua6A-259x194.jpg
1171 ms
jsd-odivelas-259x194.jpg
1262 ms
NCL-38-259x194.png
1280 ms
PCesarTeixeira20160309-259x194.png
1278 ms
CACdaPontinha-225x194.jpeg
1284 ms
background-trans.png
1374 ms
ReparacoesAgua6A-294x276.jpg
1405 ms
comm-shadow.png
1405 ms
osVerdes-60x54.jpg
1395 ms
PCesarTeixeira20160309-60x54.png
1484 ms
CAC-AG-60x54.jpg
1493 ms
JIPontinha-220x150.png
1511 ms
short-one.png
1533 ms
OrqPinteus_650-220x150.png
1520 ms
short-fiveM.png
1592 ms
PCesarTeixeira20160309-257x151.png
1598 ms
widgets.js
583 ms
plusone.js
511 ms
CAC-AG-240x151.jpg
1564 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
60 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
59 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
164 ms
sdk.js
499 ms
__utm.gif
458 ms
specificfeeds_follow.png
1412 ms
6785-featured-55x35.jpg
1423 ms
25369-featured-55x35.jpg
1442 ms
25371-featured-55x35.jpg
1492 ms
25390-featured-55x35.jpg
1161 ms
collect
172 ms
25373-featured-55x35.jpg
1159 ms
cb=gapi.loaded_0
53 ms
cb=gapi.loaded_1
128 ms
fastbutton
207 ms
25365-featured-55x35.png
1112 ms
288 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
87 ms
xd_arbiter.php
123 ms
xd_arbiter.php
196 ms
25224-featured-55x35.jpg
1045 ms
postmessageRelay
137 ms
25346-featured-55x35.jpeg
1040 ms
cb=gapi.loaded_0
50 ms
cb=gapi.loaded_1
50 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.pt.html
92 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
48 ms
25386-featured-55x35.jpg
997 ms
25380-featured-55x35.png
990 ms
3193398744-postmessagerelay.js
52 ms
rpc:shindig_random.js
52 ms
cb=gapi.loaded_0
4 ms
Autarquicas2013-DebatePL20131015-60x54.jpg
889 ms
jot
83 ms
autarquicas2013JFOdivelas-60x54.jpg
811 ms
fernandaMateus_TVL-60x54.jpg
800 ms
MiguelXara_odivelas-60x54.jpg
733 ms
sandra_pereira_odivelas-60x54.jpg
775 ms
OdivelasPb.jpg
887 ms
read-light.png
779 ms
slider-button.png
703 ms
feature.png
699 ms
odivelas.com SEO score
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Odivelas.com 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 Odivelas.com 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.
odivelas.com
Open Graph description is not detected on the main page of Odivelas. 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: