Tools & Wizards About Us
classicar.pt screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 40

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

classicar.pt

classicar.pt

Page Load Speed

4.4 sec in total

First Response

985 ms

Resources Loaded

3.1 sec

Page Rendered

335 ms

classicar.pt screenshot

About Website

Welcome to classicar.pt homepage info - get ready to check Classicar best content right away, or after learning these important things about classicar.pt

Anúncios de automóveis novos e usados, reportagens, lançamentos, notícias, eventos, preços, fichas técnicas, fotografias, vídeos, informação enciclopédica, formativa e didáctica, directório de empresa...

Visit classicar.pt

Key Findings

We analyzed Classicar.pt page load time and found that the first response time was 985 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

classicar.pt performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value4,270 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.142

78/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

classicar.pt

985 ms

geral.css

214 ms

modalbox.css

283 ms

lightbox.css

236 ms

prototype.js

750 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 477.8 kB (69%)

Content Size

689.6 kB

After Optimization

211.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Classicar.pt main page is 689.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 255.8 kB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 242.7 kB

  • Original 255.8 kB
  • After minification 170.8 kB
  • After compression 13.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 85.0 kB, which is 33% 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 242.7 kB or 95% of the original size.

Image Optimization

-23%

Potential reduce by 46.5 kB

  • Original 201.4 kB
  • After minification 154.8 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, Classicar needs image optimization as it can save up to 46.5 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-82%

Potential reduce by 182.4 kB

  • Original 223.8 kB
  • After minification 161.2 kB
  • After compression 41.4 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 182.4 kB or 82% of the original size.

CSS Optimization

-71%

Potential reduce by 6.1 kB

  • Original 8.6 kB
  • After minification 7.1 kB
  • After compression 2.5 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. Classicar.pt needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (19%)

Requests Now

78

After Optimization

63

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

classicar.pt

classicar.pt

985 ms

geral.css

geral.css

214 ms

modalbox.css

modalbox.css

283 ms

lightbox.css

lightbox.css

236 ms

prototype.js

prototype.js

750 ms

scriptaculous.js

scriptaculous.js

263 ms

modalbox.js

modalbox.js

486 ms

lightbox.js

lightbox.js

460 ms

topo.css

topo.css

367 ms

rodape.css

rodape.css

113 ms

builder.js

builder.js

135 ms

effects.js

effects.js

240 ms

fundobanner.jpg

fundobanner.jpg

251 ms

27.jpg

27.jpg

316 ms

logotipo.png

logotipo.png

278 ms

fundo.jpg

fundo.jpg

279 ms

seta.jpg

seta.jpg

253 ms

linhapontos.jpg

linhapontos.jpg

280 ms

canto_baixo_branco_esq.png

canto_baixo_branco_esq.png

364 ms

canto_baixo_branco_dir.png

canto_baixo_branco_dir.png

387 ms

canto_cima_cinza_esq.jpg

canto_cima_cinza_esq.jpg

427 ms

canto_cima_cinza_dir.jpg

canto_cima_cinza_dir.jpg

394 ms

canto_cima_dir.png

canto_cima_dir.png

408 ms

canto_baixo_cinza.png

canto_baixo_cinza.png

458 ms

canto_baixo_cinza2.png

canto_baixo_cinza2.png

492 ms

botaook.jpg

botaook.jpg

533 ms

G2009Jul28140235.jpg

G2009Jul28140235.jpg

579 ms

2009Jul28113237.jpg

2009Jul28113237.jpg

623 ms

2009Jul28142835.jpg

2009Jul28142835.jpg

650 ms

2009Jul28121011.jpg

2009Jul28121011.jpg

700 ms

2009Jul28143027.jpg

2009Jul28143027.jpg

701 ms

2009Jul28121129.jpg

2009Jul28121129.jpg

715 ms

2009Jul28121512.jpg

2009Jul28121512.jpg

716 ms

2009Jul28122613.jpg

2009Jul28122613.jpg

754 ms

2009Jul28123137.jpg

2009Jul28123137.jpg

804 ms

2009Jul28123310.jpg

2009Jul28123310.jpg

807 ms

2009Jul28142614.jpg

2009Jul28142614.jpg

811 ms

2009Jul28144848.jpg

2009Jul28144848.jpg

875 ms

2009Jul28143211.jpg

2009Jul28143211.jpg

859 ms

2009Jul28143243.jpg

2009Jul28143243.jpg

878 ms

2009Jul28143358.jpg

2009Jul28143358.jpg

912 ms

2009Jul28123427.jpg

2009Jul28123427.jpg

913 ms

2009Jul28123623.jpg

2009Jul28123623.jpg

919 ms

2009Jul28125948.jpg

2009Jul28125948.jpg

969 ms

2009Jul28130114.jpg

2009Jul28130114.jpg

1031 ms

2009Jul28143516.jpg

2009Jul28143516.jpg

1028 ms

2009Jul28143559.jpg

2009Jul28143559.jpg

1040 ms

2009Jul28133710.jpg

2009Jul28133710.jpg

976 ms

2009Jul28143829.jpg

2009Jul28143829.jpg

834 ms

2009Jul28135651.jpg

2009Jul28135651.jpg

805 ms

2009Jul28135831.jpg

2009Jul28135831.jpg

860 ms

2009Jul28143914.jpg

2009Jul28143914.jpg

865 ms

2009Jul28143948.jpg

2009Jul28143948.jpg

863 ms

2009Jul28144023.jpg

2009Jul28144023.jpg

839 ms

2009Jul28140024.jpg

2009Jul28140024.jpg

831 ms

2009Jul28140235.jpg

2009Jul28140235.jpg

809 ms

2009Jul28144142.jpg

2009Jul28144142.jpg

904 ms

2010May723015462813600.jpg

2010May723015462813600.jpg

906 ms

2009Jul28140515.jpg

2009Jul28140515.jpg

868 ms

2009Jul28140645.jpg

2009Jul28140645.jpg

837 ms

2009Jul28140743.jpg

2009Jul28140743.jpg

829 ms

2010May722575492759300.jpg

2010May722575492759300.jpg

796 ms

2009Jul28141452.jpg

2009Jul28141452.jpg

839 ms

2009Jul28141537.jpg

2009Jul28141537.jpg

844 ms

2010May722545468434300.jpg

2010May722545468434300.jpg

812 ms

2009Jul28141838.jpg

2009Jul28141838.jpg

771 ms

2009Jul28142313.jpg

2009Jul28142313.jpg

766 ms

2009Jul28144240.jpg

2009Jul28144240.jpg

755 ms

2009Jul28141757.jpg

2009Jul28141757.jpg

824 ms

2009Jul28142042.jpg

2009Jul28142042.jpg

832 ms

2009Jul28144319.jpg

2009Jul28144319.jpg

782 ms

2009Jul28141956.jpg

2009Jul28141956.jpg

779 ms

2009Jul28142139.jpg

2009Jul28142139.jpg

783 ms

2009Jul28142229.jpg

2009Jul28142229.jpg

727 ms

laranja.png

laranja.png

789 ms

amarelo.png

amarelo.png

812 ms

laranjagrande.jpg

laranjagrande.jpg

789 ms

loading.gif

loading.gif

809 ms

closelabel.jpg

closelabel.jpg

812 ms

Accessibility Review

classicar.pt accessibility score

40

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

classicar.pt best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

classicar.pt SEO score

58

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

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

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classicar.pt 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 Classicar.pt main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

classicar.pt

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