Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fisacar.com

Carros Usados Braga, Porto, Barcelos, Lisboa, Coimbra, Faro - Fisacar

Page Load Speed

2.5 sec in total

First Response

349 ms

Resources Loaded

1.7 sec

Page Rendered

492 ms

fisacar.com screenshot

About Website

Welcome to fisacar.com homepage info - get ready to check Fisacar best content for Portugal right away, or after learning these important things about fisacar.com

Fisacar Carros usados Venda baratos em Barcelos, Braga, Leça Palmeira, Porto, Aveiro, Coimbra, Lisboa

Visit fisacar.com

Key Findings

We analyzed Fisacar.com page load time and found that the first response time was 349 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

fisacar.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

fisacar.com

349 ms

www.fisacar.com

524 ms

uc.js

55 ms

js

82 ms

css

105 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 71% of them (40 requests) were addressed to the original Fisacar.com, 9% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (524 ms) belongs to the original domain Fisacar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.7 kB (14%)

Content Size

1.6 MB

After Optimization

1.4 MB

In fact, the total size of Fisacar.com main page is 1.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. 75% 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. Images take 939.6 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 89.6 kB

  • Original 120.5 kB
  • After minification 120.3 kB
  • After compression 30.9 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 89.6 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 12 B

  • Original 939.6 kB
  • After minification 939.6 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. Fisacar images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 111.5 kB

  • Original 413.7 kB
  • After minification 413.7 kB
  • After compression 302.2 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 111.5 kB or 27% of the original size.

CSS Optimization

-14%

Potential reduce by 17.7 kB

  • Original 125.1 kB
  • After minification 125.1 kB
  • After compression 107.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. Fisacar.com needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (20%)

Requests Now

49

After Optimization

39

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

Accessibility Review

fisacar.com accessibility score

74

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

fisacar.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

High

Missing source maps for large first-party JavaScript

SEO Factors

fisacar.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fisacar.com 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 Fisacar.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 data is detected on the main page of Fisacar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: