Access unicase.jp. iPhoneケース/スマホケース/スマートフォンアクセサリー通販 - UNiCASE

unicase.jp screenshot

14

Performance

Renders faster than
26% of other websites
65

Accessibility

Visual factors better than
that of 30% of websites
67

Best Practices

More advanced features
available than in
24% of websites
85

SEO

Google-friendlier than
55% of websites

First Response

318 ms

Resources Loaded

9.8 sec

Page Rendered

1 sec

unicase.jp screenshot

About Website

Welcome to unicase.jp homepage info - get ready to check UNiCASE best content for Japan right away, or after learning these important things about unicase.jp

iPhoneケースが8万点以上！おしゃれでかわいいケースや人気ハイブランドケース、おすすめの手帳型アイフォンケースやスマホケースをランキングでご紹介！5,500円以上のご注文で送料無料。13時までの注文で最短翌日お届け。実際の使用感など購入者の口コミもたくさん。

Visit unicase.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.298

40/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

unicase.jp

318 ms

unicase.jp

1483 ms

jquery.min.js

24 ms

css

34 ms

sp_menu.js

335 ms

Our browser made a total of 298 requests to load all elements on the main page. We found that 90% of them (268 requests) were addressed to the original Unicase.jp, 2% (6 requests) were made to Staticw2.yotpo.com and 2% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Unicase.jp.

Content Size

4.6 MB

After Optimization

4.1 MB

In fact, the total size of Unicase.jp main page is 4.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 505.7 kB

Original 547.8 kB
After minification 345.8 kB
After compression 42.1 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.0 kB, which is 37% 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 505.7 kB or 92% of the original size.

Image Optimization

-2%

Potential reduce by 61.6 kB

Original 4.0 MB
After minification 3.9 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. UNiCASE images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 10.7 kB

Original 92.2 kB
After minification 89.2 kB
After compression 81.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 10.7 kB or 12% of the original size.

CSS Optimization

-21%

Potential reduce by 8.9 kB

Original 42.3 kB
After minification 42.3 kB
After compression 33.4 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. Unicase.jp needs all CSS files to be minified and compressed as it can save up to 8.9 kB or 21% of the original size.

Requests Now

287

After Optimization

266

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

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

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

UTF-8

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

unicase.jp

Open Graph data is detected on the main page of UNiCASE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: