Tools & Wizards About Us
kancler.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

kancler.com

Магазин канцтоваров. Купить канцтовары оптом и в розницу

Page Load Speed

4.1 sec in total

First Response

296 ms

Resources Loaded

3.4 sec

Page Rendered

348 ms

kancler.com screenshot

About Website

Welcome to kancler.com homepage info - get ready to check Kancler best content for Ukraine right away, or after learning these important things about kancler.com

Канцтовары для учебы и работы. Товары для творчества, отдыха, порядка в доме и офисе. Выгодные цены. Доставка по Украине.

Visit kancler.com

Key Findings

We analyzed Kancler.com page load time and found that the first response time was 296 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

kancler.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value1.293

1/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

kancler.com

296 ms

kancler.com

970 ms

icons.png

260 ms

soc-google-2.png

354 ms

logo.png

388 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 86% of them (54 requests) were addressed to the original Kancler.com, 5% (3 requests) were made to Connect.facebook.net and 5% (3 requests) were made to Widgets.binotel.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Kancler.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.0 MB (78%)

Content Size

3.9 MB

After Optimization

870.2 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Kancler.com main page is 3.9 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. 50% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 600.9 kB

  • Original 646.1 kB
  • After minification 443.2 kB
  • After compression 45.3 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 202.9 kB, which is 31% 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 600.9 kB or 93% of the original size.

Image Optimization

-74%

Potential reduce by 2.1 MB

  • Original 2.9 MB
  • After minification 752.2 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. Obviously, Kancler needs image optimization as it can save up to 2.1 MB or 74% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-79%

Potential reduce by 278.4 kB

  • Original 351.1 kB
  • After minification 350.6 kB
  • After compression 72.7 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. Kancler.com needs all CSS files to be minified and compressed as it can save up to 278.4 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (42%)

Requests Now

60

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kancler.com

kancler.com

296 ms

kancler.com

kancler.com

970 ms

icons.png

icons.png

260 ms

soc-google-2.png

soc-google-2.png

354 ms

logo.png

logo.png

388 ms

logomini.png

logomini.png

387 ms

icon1.png

icon1.png

389 ms

11.png

11.png

388 ms

4.png

4.png

388 ms

9.png

9.png

477 ms

13.png

13.png

511 ms

10.png

10.png

512 ms

8.png

8.png

513 ms

6.png

6.png

513 ms

7.png

7.png

514 ms

0136678293fs.css

0136678293fs.css

866 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

773 ms

bootstrap.min.js

bootstrap.min.js

648 ms

jquery.validate.min.js

jquery.validate.min.js

648 ms

jquery.mask.min.js

jquery.mask.min.js

523 ms

jquery.chained.min.js

jquery.chained.min.js

523 ms

common.min.js

common.min.js

917 ms

common-theme.min.js

common-theme.min.js

650 ms

typeahead.bundle.min.js

typeahead.bundle.min.js

917 ms

search_suggestion.js

search_suggestion.js

775 ms

search_suggestion_autocomplete.js

search_suggestion_autocomplete.js

776 ms

owl.carousel.min.js

owl.carousel.min.js

915 ms

social_auth.min.js

social_auth.min.js

916 ms

modernizr.min.js

modernizr.min.js

921 ms

jquery.menu-aim.min.js

jquery.menu-aim.min.js

987 ms

mega-menu.min.js

mega-menu.min.js

1020 ms

owl.carousel.min.js

owl.carousel.min.js

1023 ms

dropzone.min.js

dropzone.min.js

1152 ms

star-ratings.min.js

star-ratings.min.js

1026 ms

js

js

62 ms

sdk.js

sdk.js

20 ms

fb.js

fb.js

1028 ms

load-modal-scripts.js

load-modal-scripts.js

1115 ms

43-989x289.jpg

43-989x289.jpg

1660 ms

banner-2-989x289.jpg

banner-2-989x289.jpg

1409 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1077 ms

52e2c8370efa11e9beb9002682d30847_a66e5474bf7211eab782002522f8e32e-200x200.jpg

52e2c8370efa11e9beb9002682d30847_a66e5474bf7211eab782002522f8e32e-200x200.jpg

984 ms

f8d147c30ef911e9beb9002682d30847_5c532a39bdef11eab782002522f8e32e-200x200.jpg

f8d147c30ef911e9beb9002682d30847_5c532a39bdef11eab782002522f8e32e-200x200.jpg

989 ms

50b461d50efc11e9beb9002682d30847_8c6724a6658011edbc88002522f8e32e-200x200.jpg

50b461d50efc11e9beb9002682d30847_8c6724a6658011edbc88002522f8e32e-200x200.jpg

1012 ms

50b461cb0efc11e9beb9002682d30847_20c83cffbdd411eab782002522f8e32e-200x200.jpg

50b461cb0efc11e9beb9002682d30847_20c83cffbdd411eab782002522f8e32e-200x200.jpg

1024 ms

fab420b0b30b11eba5c5002522f8e32e_45adf0d0b31c11eba5c5002522f8e32e-200x200.jpg

fab420b0b30b11eba5c5002522f8e32e_45adf0d0b31c11eba5c5002522f8e32e-200x200.jpg

1024 ms

5cad21780efc11e9beb9002682d30847_20c83d00bdd411eab782002522f8e32e-200x200.jpg

5cad21780efc11e9beb9002682d30847_20c83d00bdd411eab782002522f8e32e-200x200.jpg

1106 ms

4a6ed0160f0011e9beb9002682d30847_a68f87bcbf5011eab782002522f8e32e-200x200.jpg

4a6ed0160f0011e9beb9002682d30847_a68f87bcbf5011eab782002522f8e32e-200x200.jpg

1053 ms

7a80d0200f0011e9beb9002682d30847_f855c329c10611eaab5e002522f8e32e-200x200.jpg

7a80d0200f0011e9beb9002682d30847_f855c329c10611eaab5e002522f8e32e-200x200.jpg

1027 ms

8c8fba3f0f0011e9beb9002682d30847_23043609bf6211eab782002522f8e32e-200x200.jpg

8c8fba3f0f0011e9beb9002682d30847_23043609bf6211eab782002522f8e32e-200x200.jpg

1028 ms

a49deac70f0011e9beb9002682d30847_26a8d597bf6a11eab782002522f8e32e-200x200.jpg

a49deac70f0011e9beb9002682d30847_26a8d597bf6a11eab782002522f8e32e-200x200.jpg

1108 ms

bag-outline-1.png

bag-outline-1.png

1141 ms

Truck.png

Truck.png

1146 ms

House.png

House.png

1026 ms

logofoot.png

logofoot.png

1026 ms

problem_report.png

problem_report.png

1318 ms

sdk.js

sdk.js

45 ms

c64j8ask3jk1hzbteyt8.js

c64j8ask3jk1hzbteyt8.js

528 ms

sdk.js

sdk.js

12 ms

69 ms

css

css

35 ms

theme_5.css

theme_5.css

238 ms

getcall_utf-8.js

getcall_utf-8.js

471 ms

Accessibility Review

kancler.com accessibility score

59

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

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

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

kancler.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

kancler.com SEO score

81

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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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

kancler.com

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