Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

caseby.me

케이스바이미

Page Load Speed

19.1 sec in total

First Response

1.1 sec

Resources Loaded

17.6 sec

Page Rendered

427 ms

caseby.me screenshot

About Website

Visit caseby.me now to see the best up-to-date Caseby content for South Korea and also check out these interesting facts you probably never knew about caseby.me

caseby.me(케이스바이미)는 당신의 특별한 순간을 스마트폰 케이스로 담아내기 위해 태어났습니다. 내 개성을 드러내기에도 충분히 감각적이고, 특별한 사람에겐 ‘세상에 단 하나뿐인’ 스마트폰 케이스를 선물할 수도 있습니다. 가장 소중하고 가장 특별한 것, casebyme로 당신의 추억을 나누어주세요.

Visit caseby.me

Key Findings

We analyzed Caseby.me page load time and found that the first response time was 1.1 sec and then it took 18 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

caseby.me performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value9.0 s

15/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

caseby.me

1149 ms

home_kr.min.css

859 ms

kr.js

615 ms

home_page.min.js

1181 ms

fbds.js

30 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 80% of them (66 requests) were addressed to the original Caseby.me, 6% (5 requests) were made to Facebook.com and 4% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (15.6 sec) relates to the external source Img1.kbstar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 231.7 kB (4%)

Content Size

6.6 MB

After Optimization

6.4 MB

In fact, the total size of Caseby.me main page is 6.6 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. 60% of websites need less resources to load. Images take 6.5 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 51.9 kB

  • Original 71.2 kB
  • After minification 67.7 kB
  • After compression 19.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. 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 51.9 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 179.8 kB

  • Original 6.5 MB
  • After minification 6.3 MB

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. Caseby images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

79

After Optimization

75

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caseby. 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.

Accessibility Review

caseby.me accessibility score

33

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.

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

Image elements do not have [alt] attributes

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

caseby.me 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

caseby.me SEO score

85

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

    KO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Caseby.me can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Caseby.me 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 Caseby. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: