Tools & Wizards About Us
cano.pl screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

cano.pl

CANO.PL - Producent Materiałów reklamowych

Page Load Speed

8 sec in total

First Response

726 ms

Resources Loaded

6.9 sec

Page Rendered

354 ms

cano.pl screenshot

About Website

Welcome to cano.pl homepage info - get ready to check CANO best content right away, or after learning these important things about cano.pl

Drukarnia Cano.pl Producent Pudełek , Teczek reklamowych , Wzorników Segregatorów Reklamowych kupuj prosto od producenta

Visit cano.pl

Key Findings

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

Performance Metrics

cano.pl performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value460 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.3 s

24/100

10%

Network Requests Diagram

cano.pl

726 ms

cano.com.pl

687 ms

www.cano.com.pl

764 ms

cano_style.css

191 ms

jquery-1.11.0.min.js

671 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Cano.pl, 63% (24 requests) were made to Cano.com.pl and 8% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Cano.com.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.9 kB (26%)

Content Size

773.2 kB

After Optimization

569.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cano.pl main page is 773.2 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. 30% of websites need less resources to load. Images take 526.7 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 9.0 kB

  • Original 13.0 kB
  • After minification 11.6 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 1.4 kB, which is 11% 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 9.0 kB or 70% of the original size.

Image Optimization

-10%

Potential reduce by 52.0 kB

  • Original 526.7 kB
  • After minification 474.7 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. CANO images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 126.1 kB

  • Original 212.4 kB
  • After minification 208.8 kB
  • After compression 86.3 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 126.1 kB or 59% of the original size.

CSS Optimization

-79%

Potential reduce by 16.7 kB

  • Original 21.1 kB
  • After minification 16.0 kB
  • After compression 4.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. Cano.pl needs all CSS files to be minified and compressed as it can save up to 16.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (43%)

Requests Now

30

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CANO. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

cano.pl

cano.pl

726 ms

cano.com.pl

cano.com.pl

687 ms

www.cano.com.pl

www.cano.com.pl

764 ms

cano_style.css

cano_style.css

191 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

671 ms

lightbox.min.js

lightbox.min.js

330 ms

lightbox.css

lightbox.css

313 ms

swfobject.js

swfobject.js

344 ms

ddsmoothmenu.css

ddsmoothmenu.css

336 ms

jquery.min.js

jquery.min.js

694 ms

ddsmoothmenu.js

ddsmoothmenu.js

535 ms

script.js

script.js

369 ms

cachedscriptxy.js

cachedscriptxy.js

292 ms

close.png

close.png

143 ms

loading.gif

loading.gif

186 ms

prev.png

prev.png

230 ms

next.png

next.png

199 ms

logo.png

logo.png

286 ms

cano_menu_hover.png

cano_menu_hover.png

295 ms

cano_smm.png

cano_smm.png

415 ms

cano_middle.jpg

cano_middle.jpg

3369 ms

opakowanie.jpg

opakowanie.jpg

1980 ms

page1-img1.jpg

page1-img1.jpg

1190 ms

page1-img2.jpg

page1-img2.jpg

1093 ms

page1-img3.jpg

page1-img3.jpg

1256 ms

page1-img4.jpg

page1-img4.jpg

1681 ms

onas.jpg

onas.jpg

3261 ms

analytics.js

analytics.js

55 ms

xnZs0aVnpdc

xnZs0aVnpdc

122 ms

collect

collect

19 ms

www-embed-player-vfl5foy2V.css

www-embed-player-vfl5foy2V.css

131 ms

www-embed-player.js

www-embed-player.js

182 ms

base.js

base.js

642 ms

rexdot.gif

rexdot.gif

180 ms

veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js

veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js

78 ms

ad_status.js

ad_status.js

77 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

117 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

115 ms

Accessibility Review

cano.pl accessibility score

82

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

Page has valid source maps

SEO Factors

cano.pl SEO score

91

Search Engine Optimization Advices

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

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cano.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 Cano.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

cano.pl

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