15.8 sec in total
2.4 sec
12.9 sec
550 ms
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万点以上!おしゃれでかわいいケースや人気ハイブランドケース、おすすめの手帳型アイフォンケースやスマホケースをランキングでご紹介!お近くの店舗の在庫も確認できます。13時までの注文で最短翌日お届け。実際の使用感など購入者の口コミもたくさん。
Visit unicase.jpWe analyzed Unicase.jp page load time and found that the first response time was 2.4 sec and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
unicase.jp performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value8.2 s
2/100
25%
Value12.4 s
3/100
10%
Value2,610 ms
4/100
30%
Value0.334
34/100
15%
Value13.4 s
11/100
10%
2362 ms
1760 ms
40 ms
895 ms
1071 ms
Our browser made a total of 279 requests to load all elements on the main page. We found that 96% of them (268 requests) were addressed to the original Unicase.jp, 1% (4 requests) were made to Google-analytics.com and 1% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Unicase.jp.
Page size can be reduced by 559.2 kB (14%)
4.0 MB
3.4 MB
In fact, the total size of Unicase.jp main page is 4.0 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. 70% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 278.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 106.9 kB, which is 35% 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 278.9 kB or 91% of the original size.
Potential reduce by 51.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. UNiCASE images are well optimized though.
Potential reduce by 91.4 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 91.4 kB or 59% of the original size.
Potential reduce by 137.2 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 137.2 kB or 86% of the original size.
Number of requests can be reduced by 19 (7%)
270
251
The browser has sent 270 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 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
{{url}}
{{time}} ms
unicase.jp accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
unicase.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
unicase.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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.
{{og_description}}
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: