6.1 sec in total
1.1 sec
4.7 sec
380 ms
Visit vigobloco.pt now to see the best up-to-date Vigobloco content and also check out these interesting facts you probably never knew about vigobloco.pt
A Vigobloco é líder em Portugal na fabricação de produtos de betão para a construção. Concebemos, produzimos e montamos soluções pré-fabricadas de betão.
Visit vigobloco.ptWe analyzed Vigobloco.pt page load time and found that the first response time was 1.1 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
vigobloco.pt performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value27.3 s
0/100
25%
Value15.7 s
0/100
10%
Value1,840 ms
9/100
30%
Value0.752
6/100
15%
Value18.5 s
3/100
10%
1060 ms
352 ms
438 ms
222 ms
222 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 78% of them (97 requests) were addressed to the original Vigobloco.pt, 17% (21 requests) were made to Static.xx.fbcdn.net and 2% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Vigobloco.pt.
Page size can be reduced by 996.5 kB (15%)
6.6 MB
5.6 MB
In fact, the total size of Vigobloco.pt main page is 6.6 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 5.7 MB which makes up the majority of the site volume.
Potential reduce by 56.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 8.5 kB, which is 13% 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 56.1 kB or 83% of the original size.
Potential reduce by 300.0 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. Vigobloco images are well optimized though.
Potential reduce by 397.1 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 397.1 kB or 72% of the original size.
Potential reduce by 243.3 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. Vigobloco.pt needs all CSS files to be minified and compressed as it can save up to 243.3 kB or 86% of the original size.
Number of requests can be reduced by 62 (51%)
122
60
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vigobloco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
vigobloco.pt
1060 ms
modal.css
352 ms
k2.css
438 ms
system.css
222 ms
general.css
222 ms
module_default.css
610 ms
rokajaxsearch.css
325 ms
rokajaxsearch-theme.css
330 ms
style.css
329 ms
addons.css
434 ms
layout.css
440 ms
template.css
548 ms
usertools.css
460 ms
css3.css
542 ms
mega.css
544 ms
typo.css
657 ms
template.css
894 ms
mega.css
652 ms
k2-style.css
654 ms
portfolio.css
667 ms
mootools-core.js
1044 ms
core.js
760 ms
mootools-more.js
1206 ms
modal.js
764 ms
k2.js
771 ms
jquery.js
1085 ms
jqscripts.js
872 ms
core.js
880 ms
mega.js
1092 ms
selectivizr-min.js
993 ms
acymailing_module.js
996 ms
jquery.quicksand.js
1104 ms
script.js
1106 ms
besps.js
1147 ms
rokajaxsearch.js
1198 ms
besps.css
1199 ms
css
26 ms
system.css
1006 ms
arrow.cur
149 ms
banner.jpg
452 ms
001.jpg
339 ms
002.jpg
342 ms
003.jpg
332 ms
fotografia.jpg
456 ms
fotografia1.JPG
841 ms
fotografia2.JPG
1215 ms
001.jpg
1022 ms
01.jpg
2424 ms
ale.jpg
1000 ms
foto1.jpg
568 ms
foto2.jpg
747 ms
foto3.jpg
992 ms
02.jpg
995 ms
03.jpg
996 ms
05.jpg
1021 ms
data.png
1260 ms
france.jpg
1102 ms
vgb.jpg
1102 ms
7acce66d40ec90c2d61987b409cbf850_S.jpg
1141 ms
f0ba2bfd8f936a77d3b146acfe9443c7_S.jpg
1213 ms
5fa21cd9e0d2531a2f1dfdffbab46f70_S.jpg
1218 ms
2722f6bcd13027c06fe9d3b0e6f955cf_S.jpg
1243 ms
ee68a9df1200997b07be8fb0bbdb9f29_S.jpg
1315 ms
133.jpg
1315 ms
148.jpg
1313 ms
137.jpg
1336 ms
152.jpg
1350 ms
132.jpg
1407 ms
131.jpg
1421 ms
134.jpg
1423 ms
139.jpg
1446 ms
138.jpg
1459 ms
154.jpg
1516 ms
all.js
92 ms
125.jpg
1513 ms
163.jpg
1430 ms
154 ms
xd_arbiter.php
62 ms
xd_arbiter.php
125 ms
comments.php
184 ms
126.jpg
1267 ms
124.jpg
1274 ms
122.jpg
1324 ms
123.jpg
1237 ms
121.jpg
1229 ms
ebiMDO3r-8l.css
109 ms
jGc-59L_9lo.css
126 ms
1M-hNYiGrgS.css
149 ms
uVjHKJ0glvg.css
186 ms
TKuNj0xVh4A.js
185 ms
FJmpeSpHpjS.js
232 ms
0wM5s1Khldu.js
169 ms
LTv6ZK-5zxz.js
248 ms
1FCa-btixu2.js
230 ms
Oagsvfb4VWi.js
247 ms
FyxLoiww5bU.js
285 ms
HaMjR2eXz4B.js
284 ms
WN2wSsLOuKy.js
316 ms
Kt4tkgSRvHH.js
315 ms
Q4A0UyjU8W2.js
326 ms
1bNoFZUdlYZ.js
347 ms
135.jpg
1135 ms
118.jpg
935 ms
fav.png
22 ms
wL6VQj7Ab77.png
35 ms
117.jpg
773 ms
K00K-UgnsKu.png
24 ms
120.jpg
788 ms
116.jpg
791 ms
156.jpg
818 ms
119.jpg
808 ms
159.jpg
862 ms
eR-qA8bp1RM.js
20 ms
I6-MnjEovm5.js
24 ms
pQrUxxo5oQp.js
39 ms
480px-facebook_logo_square.png
874 ms
logo.png
794 ms
mask-strong.png
821 ms
arrow-w2.png
787 ms
menu.png
782 ms
search-bg.png
786 ms
search-icon.png
785 ms
home-small.png
789 ms
top.png
779 ms
pb.png
778 ms
vigobloco.pt 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
vigobloco.pt 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
vigobloco.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vigobloco.pt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Vigobloco.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.
vigobloco.pt
Open Graph description is not detected on the main page of Vigobloco. 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: