Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fiat.pt

FIAT Portugal - Site oficial | Fiat.pt

Page Load Speed

7 sec in total

First Response

2.2 sec

Resources Loaded

4.3 sec

Page Rendered

533 ms

fiat.pt screenshot

About Website

Visit fiat.pt now to see the best up-to-date FIAT content for Portugal and also check out these interesting facts you probably never knew about fiat.pt

Bem vindo à página oficial da Fiat Portugal. Descobre a gama de carros novos e solicita um test-drive

Visit fiat.pt

Key Findings

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

Performance Metrics

fiat.pt performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value3,840 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.838

4/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

www.fiat.pt

2217 ms

init.js

205 ms

fiatribbonscript.js

108 ms

960_12_col.css

17 ms

screen.css

99 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 73% of them (92 requests) were addressed to the original Fiat.pt, 4% (5 requests) were made to Cookielaw.emea.fcagroup.com and 3% (4 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Fiat.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.8 MB (36%)

Content Size

7.8 MB

After Optimization

5.0 MB

In fact, the total size of Fiat.pt main page is 7.8 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. 85% 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 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 94.4 kB

  • Original 125.9 kB
  • After minification 120.1 kB
  • After compression 31.6 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 94.4 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 206.3 kB

  • Original 4.4 MB
  • After minification 4.2 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. FIAT images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 2.1 MB

  • Original 2.7 MB
  • After minification 2.3 MB
  • After compression 659.8 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 2.1 MB or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 470.8 kB

  • Original 552.6 kB
  • After minification 447.9 kB
  • After compression 81.8 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. Fiat.pt needs all CSS files to be minified and compressed as it can save up to 470.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 69 (58%)

Requests Now

118

After Optimization

49

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

Accessibility Review

fiat.pt accessibility score

81

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.

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

<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

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

fiat.pt best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

fiat.pt SEO score

86

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

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

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fiat.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 Fiat.pt main page’s claimed encoding is windows-1252. 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

Open Graph data is detected on the main page of FIAT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: