4 sec in total
386 ms
3.3 sec
394 ms
Welcome to albinovieira.com homepage info - get ready to check Albino Vieira best content for Portugal right away, or after learning these important things about albinovieira.com
Your website description.
Visit albinovieira.comWe analyzed Albinovieira.com page load time and found that the first response time was 386 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
albinovieira.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value9.8 s
0/100
25%
Value12.5 s
3/100
10%
Value640 ms
46/100
30%
Value0.174
69/100
15%
Value16.8 s
5/100
10%
386 ms
113 ms
221 ms
223 ms
332 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 67% of them (61 requests) were addressed to the original Albinovieira.com, 3% (3 requests) were made to Fonts.googleapis.com and 3% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Albinovieira.com.
Page size can be reduced by 485.7 kB (19%)
2.5 MB
2.1 MB
In fact, the total size of Albinovieira.com main page is 2.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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 76.8 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 76.8 kB or 73% of the original size.
Potential reduce by 24.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. Albino Vieira images are well optimized though.
Potential reduce by 342.9 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 342.9 kB or 61% of the original size.
Potential reduce by 41.9 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. Albinovieira.com needs all CSS files to be minified and compressed as it can save up to 41.9 kB or 83% of the original size.
Number of requests can be reduced by 65 (74%)
88
23
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Albino Vieira. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
albinovieira.com
386 ms
style.css
113 ms
css_browser_selector.js
221 ms
navigation.css
223 ms
jquery.min.js
332 ms
text-3628c4bb-fcfa-e13d-182d-3044903db446.css
223 ms
text.css
226 ms
text.js
227 ms
text-d8da9071-6050-e2f2-8634-778a33fa0d67.css
327 ms
css
28 ms
text-93555f60-5703-4ea2-bd6d-0a36bc781922.css
326 ms
navigation-04eb4af7-c852-4a9e-b7da-834f3984d30c.css
327 ms
css
39 ms
text-4b067c7c-742d-47c0-b63a-174554a06fd6.css
343 ms
header-3996124b-e2aa-4e0c-aced-42b82a43fe10.css
341 ms
breadcrumbs-0f7c1824-1e47-2633-a586-dff4036871e6.css
432 ms
css
47 ms
text-9cec5cea-228f-40f0-bc70-1c1b53e5f378.css
434 ms
text-dab18eed-546b-4571-b496-5af16bbdcac3.css
433 ms
text-e3221003-94e9-86af-1702-85ed20295abe.css
434 ms
text-4434d6cb-3e71-4b41-abae-31ee58d8cbc7.css
436 ms
text-55b77ade-df2d-4560-a406-036d074b2e8b.css
438 ms
text-a67094e4-4c21-411c-a62e-2522bb6c0d68.css
536 ms
addthis_widget.js
12 ms
navigation-2ecddb19-7b6c-408f-8796-6d2f72fc7a61.css
581 ms
text-58f4bf1e-ed61-444d-ba6e-51407ed87e96.css
581 ms
layout.css
581 ms
helpers.js
581 ms
view.js
581 ms
getcod.cgi
305 ms
anti_cache.js
645 ms
pr.chromefans.org
163 ms
bg1_1.jpg
554 ms
external-border-none-top-left.png
153 ms
external-border-none-top-right.png
153 ms
external-border-none-top.png
152 ms
external-border-none-top-left2.png
153 ms
external-border-none-top-right2.png
168 ms
external-border-none-left.png
219 ms
external-border-none-left-top.png
220 ms
external-border-none-left-bottom.png
222 ms
external-border-none-right.png
221 ms
external-border-none-right-top.png
277 ms
external-border-none-right-bottom.png
326 ms
external-border-none-bottom-left.png
327 ms
external-border-none-bottom-right.png
327 ms
external-border-none-bottom.png
328 ms
external-border-none-bottom-left2.png
383 ms
external-border-none-bottom-right2.png
434 ms
top_bg_5.png
435 ms
border-none-top-left.png
436 ms
border-none-top-right.png
436 ms
border-none-top.png
493 ms
border-none-left.png
551 ms
border-none-right.png
550 ms
logo-e-nome-grande.png
871 ms
menu-toggle.png
550 ms
published_image_0.png
709 ms
home.gif
658 ms
border-none-bottom-left.png
661 ms
border-none-bottom-right.png
661 ms
border-none-bottom.png
660 ms
black_opacity_30.png
767 ms
alambique-coluna-5lts_1.png
1203 ms
Alambique-prodution.jpg
1852 ms
map.js
207 ms
gTHiwyxi6S7iiHpqAoiE3NqQynqKV_9Plp7mupa0S4g.ttf
33 ms
WZDISdyil4HsmirlOdBRFNqQynqKV_9Plp7mupa0S4g.ttf
77 ms
shinystat.cgi
304 ms
black_opacity_31.png
750 ms
bg2.jpg
799 ms
300lo.json
70 ms
all.js&version=v2.0
385 ms
widgets.js
9 ms
sh.7c7179124ea24ac6ba46caac.html
56 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
40 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
14 ms
jquery.min.js
67 ms
widget_call_home.js
296 ms
map_v2_loading.png
127 ms
jot
86 ms
logo4-small.png
132 ms
140 ms
xd_arbiter.php
139 ms
xd_arbiter.php
252 ms
map
80 ms
map_v2-control.png
69 ms
ping
33 ms
like.php
61 ms
vpc6VNjRPXV.js
271 ms
LVx-xkvaJ0b.png
303 ms
albinovieira.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
albinovieira.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
albinovieira.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Albinovieira.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Albinovieira.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.
albinovieira.com
Open Graph description is not detected on the main page of Albino Vieira. 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: