Tools & Wizards About Us
continental.pl screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

continental.pl

Continental Polska

Page Load Speed

10 sec in total

First Response

308 ms

Resources Loaded

9.1 sec

Page Rendered

601 ms

continental.pl screenshot

About Website

Click here to check amazing Continental content for Poland. Otherwise, check out these important facts you probably never knew about continental.pl

Szukasz niezawodnych opon samochodowych? Zapoznaj się z szeroką ofertą opon Continental. Znajdź punkty sprzedaży opon Continental w najbliższej okolicy!

Visit continental.pl

Key Findings

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

Performance Metrics

continental.pl performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.296

40/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

continental.pl

308 ms

samochod

2103 ms

picturefill.min.js

285 ms

footerStory-8f8f7c18.css

387 ms

main-abb7d2a1.css

613 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Continental.pl, 48% (28 requests) were made to Blobs.continental-tires.com and 43% (25 requests) were made to Continental-opony.pl. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Blobs.continental-tires.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 134.4 kB (76%)

Content Size

176.7 kB

After Optimization

42.3 kB

  • HTML
  • JavaScript

In fact, the total size of Continental.pl main page is 176.7 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. 45% of websites need less resources to load. HTML takes 131.6 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 118.8 kB

  • Original 131.6 kB
  • After minification 93.9 kB
  • After compression 12.8 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 37.7 kB, which is 29% 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 118.8 kB or 90% of the original size.

JavaScript Optimization

-35%

Potential reduce by 15.6 kB

  • Original 45.2 kB
  • After minification 45.2 kB
  • After compression 29.5 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 15.6 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (8%)

Requests Now

52

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

continental.pl

continental.pl

308 ms

samochod

samochod

2103 ms

picturefill.min.js

picturefill.min.js

285 ms

footerStory-8f8f7c18.css

footerStory-8f8f7c18.css

387 ms

main-abb7d2a1.css

main-abb7d2a1.css

613 ms

continental_logo-9e4b34b6.svg

continental_logo-9e4b34b6.svg

319 ms

continental_claim-fa327085.svg

continental_claim-fa327085.svg

319 ms

stage-image-mundial.jpg

stage-image-mundial.jpg

356 ms

stage-image-winter2015.jpg

stage-image-winter2015.jpg

580 ms

stage-image-oe.jpg

stage-image-oe.jpg

615 ms

stage-image-why-conti.jpg

stage-image-why-conti.jpg

605 ms

stage-image-contiseal.jpg

stage-image-contiseal.jpg

605 ms

contiwintercontact-ts-810-tire-image.png

contiwintercontact-ts-810-tire-image.png

891 ms

contiwintercontact-ts-810-sport-tire-image.png

contiwintercontact-ts-810-sport-tire-image.png

981 ms

contiwintercontact-ts-830-tire-image.png

contiwintercontact-ts-830-tire-image.png

1025 ms

contiwintercontact-ts-830-p-tire-image.png

contiwintercontact-ts-830-p-tire-image.png

639 ms

contiwintercontact-ts-850-tire-image.png

contiwintercontact-ts-850-tire-image.png

643 ms

wintercontact-ts-850p-tire-image.png

wintercontact-ts-850p-tire-image.png

643 ms

conti4x4wintercontact-tire-image.png

conti4x4wintercontact-tire-image.png

678 ms

conticrosscontact-winter-tire-image.png

conticrosscontact-winter-tire-image.png

687 ms

vancowinter2-tire-image.png

vancowinter2-tire-image.png

1195 ms

arrow-up-3b56c4ef.svg

arrow-up-3b56c4ef.svg

218 ms

main-313b6a37.js

main-313b6a37.js

1403 ms

stage-image-mundial.jpg

stage-image-mundial.jpg

3402 ms

stage-image-winter2015.jpg

stage-image-winter2015.jpg

3400 ms

stage-image-oe.jpg

stage-image-oe.jpg

3400 ms

stage-image-why-conti.jpg

stage-image-why-conti.jpg

3401 ms

stage-image-contiseal.jpg

stage-image-contiseal.jpg

3399 ms

sponsoring-01-image.jpg

sponsoring-01-image.jpg

979 ms

tested-for-your-safety-image0.jpg

tested-for-your-safety-image0.jpg

979 ms

stage_shadow-4002f387.png

stage_shadow-4002f387.png

430 ms

bg_grey_tile-22204895.jpg

bg_grey_tile-22204895.jpg

295 ms

bg_tirefinder_plt-72c05747.jpg

bg_tirefinder_plt-72c05747.jpg

384 ms

tire_shadow_thumbnail-c2f717e3.png

tire_shadow_thumbnail-c2f717e3.png

199 ms

bg_dealer_locator-841cf1d8.jpg

bg_dealer_locator-841cf1d8.jpg

737 ms

bg_black_tile-638b9bcb.jpg

bg_black_tile-638b9bcb.jpg

592 ms

ContinentalStagSansWeb-Book-735ef154.woff

ContinentalStagSansWeb-Book-735ef154.woff

689 ms

ContinentalStagSansWeb-Medium-6e97fb77.woff

ContinentalStagSansWeb-Medium-6e97fb77.woff

775 ms

ContinentalIcon-80d8ab28.woff

ContinentalIcon-80d8ab28.woff

596 ms

ContinentalStagSansWeb-Light-392ed133.woff

ContinentalStagSansWeb-Light-392ed133.woff

3038 ms

293114

293114

222 ms

293114

293114

236 ms

293114

293114

3106 ms

293114

293114

230 ms

293114

293114

303 ms

webtrends.min.js

webtrends.min.js

172 ms

gtm.js

gtm.js

171 ms

socialNews

socialNews

252 ms

dcs.gif

dcs.gif

46 ms

analytics.js

analytics.js

8 ms

collect

collect

10 ms

sportowe-opony-zdobywaja-rynek-img-1.jpg

sportowe-opony-zdobywaja-rynek-img-1.jpg

390 ms

sportcontact-6-img-2.jpg

sportcontact-6-img-2.jpg

244 ms

1.jpg

1.jpg

232 ms

wardsauto-2016-best-engines.jpg

wardsauto-2016-best-engines.jpg

350 ms

globalny-dialog-continental-1.jpg

globalny-dialog-continental-1.jpg

394 ms

inteligentne-szyby-samochodowe-continental.jpg

inteligentne-szyby-samochodowe-continental.jpg

245 ms

print-ee86f9f1.css

print-ee86f9f1.css

234 ms

Accessibility Review

continental.pl accessibility score

75

Accessibility Issues

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

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.

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

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

High

Missing source maps for large first-party JavaScript

SEO Factors

continental.pl SEO score

92

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

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

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Continental.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Continental.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

continental.pl

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