Tools & Wizards About Us
caseme.by screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

caseme.by

Чехлы для телефонов на заказ с фотографией, именные, с логотипом купить в интернет-магазине caseme.by

Page Load Speed

4.9 sec in total

First Response

710 ms

Resources Loaded

3.6 sec

Page Rendered

596 ms

caseme.by screenshot

About Website

Visit caseme.by now to see the best up-to-date Caseme content for Belarus and also check out these interesting facts you probably never knew about caseme.by

Купить чехлы с фотографией, с дизайном, с именем, с логотипом для телефонов Apple, Xiaomi, Huawei, Samsung, Honor и др. Высокое качество. Отличный сервис. Быстрое изготовление. Доставка по Минску и вс...

Visit caseme.by

Key Findings

We analyzed Caseme.by page load time and found that the first response time was 710 ms and then it took 4.2 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

caseme.by performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

caseme.by

710 ms

caseme.by

1456 ms

common.css

121 ms

manifest.js

235 ms

vendor.js

705 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 98% of them (52 requests) were addressed to the original Caseme.by, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Caseme.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.2 kB (50%)

Content Size

289.5 kB

After Optimization

143.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Caseme.by main page is 289.5 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. 40% of websites need less resources to load. HTML takes 173.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 145.4 kB

  • Original 173.0 kB
  • After minification 169.3 kB
  • After compression 27.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 145.4 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 93.1 kB
  • After minification 93.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. Caseme images are well optimized though.

CSS Optimization

-3%

Potential reduce by 772 B

  • Original 23.4 kB
  • After minification 23.4 kB
  • After compression 22.6 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. Caseme.by has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (20%)

Requests Now

51

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

caseme.by

caseme.by

710 ms

caseme.by

caseme.by

1456 ms

common.css

common.css

121 ms

manifest.js

manifest.js

235 ms

vendor.js

vendor.js

705 ms

common.js

common.js

354 ms

gtm.js

gtm.js

90 ms

icon-arrow-right-white.svg

icon-arrow-right-white.svg

202 ms

icon-arrow-right-blue.svg

icon-arrow-right-blue.svg

200 ms

new.svg

new.svg

316 ms

sale.svg

sale.svg

318 ms

popular.svg

popular.svg

316 ms

cart-white.svg

cart-white.svg

333 ms

logo.svg

logo.svg

336 ms

icon-close-white.svg

icon-close-white.svg

431 ms

search.svg

search.svg

433 ms

preloader.svg

preloader.svg

435 ms

group-2.svg

group-2.svg

442 ms

Viber%201.svg

Viber%201.svg

446 ms

group-5.svg

group-5.svg

547 ms

icon-select-arrow.svg

icon-select-arrow.svg

550 ms

belarus.webp

belarus.webp

785 ms

avto.webp

avto.webp

660 ms

football.webp

football.webp

667 ms

secundomer.svg

secundomer.svg

662 ms

garantia.svg

garantia.svg

665 ms

vector-1.svg

vector-1.svg

666 ms

Group.svg

Group.svg

769 ms

iphone_13_2508_black.webp

iphone_13_2508_black.webp

777 ms

iphone_13_3107_black.webp

iphone_13_3107_black.webp

783 ms

iphone_13_4001.1_black.webp

iphone_13_4001.1_black.webp

898 ms

iphone_13_5405.2_black.webp

iphone_13_5405.2_black.webp

778 ms

iphone_13_6201.1_black.webp

iphone_13_6201.1_black.webp

878 ms

iphone_13_6208.1_black.webp

iphone_13_6208.1_black.webp

894 ms

iphone_13_6706_black.webp

iphone_13_6706_black.webp

890 ms

iphone_13_7706_black.webp

iphone_13_7706_black.webp

899 ms

bg-special-case-block.png

bg-special-case-block.png

1018 ms

foto.webp

foto.webp

1096 ms

crown.webp

crown.webp

1000 ms

korp.webp

korp.webp

1009 ms

avto.webp

avto.webp

1053 ms

644831b2105f1839842648.webp

644831b2105f1839842648.webp

820 ms

644831b905718806525003.webp

644831b905718806525003.webp

913 ms

64483193f1454945645411.webp

64483193f1454945645411.webp

927 ms

6448319d8a14f341625355.webp

6448319d8a14f341625355.webp

820 ms

644832021f351263650622.webp

644832021f351263650622.webp

822 ms

6448320952f31676937928.webp

6448320952f31676937928.webp

891 ms

6448325656126449270971.webp

6448325656126449270971.webp

891 ms

6448325c98054608989343.webp

6448325c98054608989343.webp

908 ms

644832474a9b3846682712.webp

644832474a9b3846682712.webp

818 ms

6448324cefe64512335287.webp

6448324cefe64512335287.webp

818 ms

6448314b644bc889879819.webp

6448314b644bc889879819.webp

821 ms

help-block.webp

help-block.webp

876 ms

Accessibility Review

caseme.by accessibility score

76

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

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.

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 IDs 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

caseme.by best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

caseme.by SEO score

91

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

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 Caseme.by 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 Caseme.by 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

caseme.by

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