Access rostos.pt. Dr Lisete um nome inscrito na historia do Barreiro - O Alto do Seixalinho esta no meu coraca

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value8,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.251

49/100

15%

TTI (Time to Interactive)

Value28.0 s

0/100

10%

rostos.pt

301 ms

www.rostos.pt

447 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Rostos.pt and no external sources were called. The less responsive or slowest element that took the longest time to load (447 ms) belongs to the original domain Rostos.pt.

Content Size

2.6 MB

After Optimization

2.4 MB

In fact, the total size of Rostos.pt main page is 2.6 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-35%

Potential reduce by 128 B

Original 361 B
After minification 361 B
After compression 233 B

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 128 B or 35% of the original size.

Image Optimization

-5%

Potential reduce by 125.4 kB

Original 2.5 MB
After minification 2.3 MB

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. Rostos images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 33.9 kB

Original 86.8 kB
After minification 85.2 kB
After compression 52.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 33.9 kB or 39% of the original size.

CSS Optimization

-84%

Potential reduce by 5.0 kB

Original 5.9 kB
After minification 5.0 kB
After compression 941 B

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. Rostos.pt needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 84% of the original size.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rostos.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 Rostos.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.

Social Sharing Optimization

rostos.pt

Open Graph description is not detected on the main page of Rostos. 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: