Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

filipepinto.com

Os melhores carros usados, novos e Seminovos - Porto, Marco de Canaveses.

Page Load Speed

4.8 sec in total

First Response

910 ms

Resources Loaded

3.4 sec

Page Rendered

439 ms

filipepinto.com screenshot

About Website

Click here to check amazing Filipepinto content for Portugal. Otherwise, check out these important facts you probably never knew about filipepinto.com

Encontre os melhores automoveis usados aos melhores preços, todas as marcas. Entregas em todo o país. A sua pesquisa acabou! O seu carro usado está aqui!

Visit filipepinto.com

Key Findings

We analyzed Filipepinto.com page load time and found that the first response time was 910 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

filipepinto.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.1 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value1,270 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value25.9 s

0/100

10%

Network Requests Diagram

filipepinto.com

910 ms

fontello.css

211 ms

masterslider.css

208 ms

awesomplete.css

210 ms

owl.carousel.css

213 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 65% of them (82 requests) were addressed to the original Filipepinto.com, 12% (15 requests) were made to Cdn.easysite.pt and 7% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cdn.easysite.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (53%)

Content Size

4.2 MB

After Optimization

1.9 MB

In fact, the total size of Filipepinto.com main page is 4.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 138.6 kB

  • Original 165.7 kB
  • After minification 134.0 kB
  • After compression 27.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 31.7 kB, which is 19% 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 138.6 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 83.2 kB

  • Original 1.1 MB
  • After minification 1.1 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. Filipepinto images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 1.3 MB

  • Original 2.0 MB
  • After minification 1.8 MB
  • After compression 712.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 1.3 MB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 734.2 kB

  • Original 871.6 kB
  • After minification 680.6 kB
  • After compression 137.4 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. Filipepinto.com needs all CSS files to be minified and compressed as it can save up to 734.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (63%)

Requests Now

113

After Optimization

42

The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Filipepinto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

filipepinto.com accessibility score

70

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

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

Impact

Issue

High

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

filipepinto.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

filipepinto.com SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

Content Best Practices

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

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