Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

intercars.pl

Sklep motoryzacyjny: części samochodowe online | Intercars.pl

Page Load Speed

5.7 sec in total

First Response

50 ms

Resources Loaded

4.4 sec

Page Rendered

1.2 sec

intercars.pl screenshot

About Website

Welcome to intercars.pl homepage info - get ready to check Intercars best content for Poland right away, or after learning these important things about intercars.pl

Sklep motoryzacyjny Inter Cars ➤ największy sprzedawca części samochodowych oraz opon. W ofercie posiadamy ponad 2 mln części! Sprawdź naszą ofertę!

Visit intercars.pl

Key Findings

We analyzed Intercars.pl page load time and found that the first response time was 50 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

intercars.pl performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

az.intercars.pl

50 ms

intercars.pl

1448 ms

osano.js

521 ms

all.min.css

102 ms

material-design-iconic-font.min.css

41 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 46% of them (41 requests) were addressed to the original Intercars.pl, 31% (28 requests) were made to Cmscontent.intercars.eu and 10% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Intercars.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 380.4 kB (34%)

Content Size

1.1 MB

After Optimization

726.5 kB

In fact, the total size of Intercars.pl main page is 1.1 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. Only a small number of websites need less resources to load. Javascripts take 405.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 307.1 kB

  • Original 362.1 kB
  • After minification 362.0 kB
  • After compression 55.0 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 307.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-18%

Potential reduce by 73.3 kB

  • Original 405.4 kB
  • After minification 405.4 kB
  • After compression 332.1 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 73.3 kB or 18% of the original size.

CSS Optimization

-0%

Potential reduce by 37 B

  • Original 279.3 kB
  • After minification 279.3 kB
  • After compression 279.3 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. Intercars.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (82%)

Requests Now

45

After Optimization

8

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

Accessibility Review

intercars.pl accessibility score

67

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 progressbar elements do not have accessible names.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<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

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

[id] attributes on active, focusable elements are not unique

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

intercars.pl 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

SEO Factors

intercars.pl SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intercars.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Intercars.pl 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 Intercars. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: