7.2 sec in total
335 ms
5.8 sec
1.1 sec
Welcome to phocase.jp homepage info - get ready to check Phocase best content for Japan right away, or after learning these important things about phocase.jp
{{ collections.all.all_products_count | times: 100 | money_without_currency }}点を取り揃えるスマホケース専門店。人気のおしゃれなスマホケースならcaseplay jam!
Visit phocase.jpWe analyzed Phocase.jp page load time and found that the first response time was 335 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
phocase.jp performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value18.2 s
0/100
25%
Value9.8 s
10/100
10%
Value2,240 ms
6/100
30%
Value0.345
32/100
15%
Value17.1 s
4/100
10%
335 ms
864 ms
480 ms
1358 ms
61 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 49% of them (36 requests) were addressed to the original Phocase.jp, 7% (5 requests) were made to Img.case-store.net and 5% (4 requests) were made to Log1.mobylog.jp. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Phocase.jp.
Page size can be reduced by 631.3 kB (27%)
2.3 MB
1.7 MB
In fact, the total size of Phocase.jp main page is 2.3 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. 35% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 77.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. This page needs HTML code to be minified as it can gain 12.0 kB, which is 13% 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 77.6 kB or 83% of the original size.
Potential reduce by 67.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. Phocase images are well optimized though.
Potential reduce by 332.8 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 332.8 kB or 51% of the original size.
Potential reduce by 153.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. Phocase.jp needs all CSS files to be minified and compressed as it can save up to 153.6 kB or 83% of the original size.
Number of requests can be reduced by 35 (52%)
67
32
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phocase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
phocase.jp
335 ms
phocase.jp
864 ms
common.min.css
480 ms
app.js
1358 ms
ld.js
61 ms
s_retargeting.js
970 ms
conversion.js
48 ms
json.php
964 ms
json.php
972 ms
tracker.js
194 ms
sdk.js
391 ms
deliv-free.png
178 ms
w_wr_20048.jpg
788 ms
logo.png
263 ms
icon_menu_1fav.png
319 ms
icon_menu_2cart.png
432 ms
dialog_title.png
493 ms
mirrorcase.jpg
784 ms
whiteday2016.jpg
1372 ms
season_winter2015.jpg
853 ms
main_image.jpg
1274 ms
diary.jpg
1109 ms
battery.jpg
1287 ms
main_strap.png
1233 ms
icon_ttl_diary.png
1012 ms
icon_ranking_rank1.png
1171 ms
dummy.gif
1279 ms
btn_fav.png
1328 ms
icon_ranking_rank2.png
1377 ms
icon_ranking_rank3.png
1443 ms
icon_ranking_rank4.png
1447 ms
icon_ranking_rank5.png
1443 ms
icon_ttl_hard.png
1487 ms
icon_ttl_battery.png
1518 ms
icon_ttl_new.png
1523 ms
icon_new_item.png
1611 ms
icon_ttl_news.png
1599 ms
top_contents_4.jpg
1613 ms
line.jpg
1644 ms
icon_ttl_fearure.png
1665 ms
footer_contact.png
1669 ms
footer_calendar.png
1758 ms
ban_insta.jpg
1778 ms
analytics.js
67 ms
gtm.js
175 ms
tag.js
87 ms
101 ms
fontawesome-webfont.woff
1711 ms
fbds.js
235 ms
01_0022_0136_c01_ip6_m03.jpg
1213 ms
01_0070_0258_c09_ip6_m03.jpg
835 ms
01_0088_0016_c15_ip6_m03.jpg
1169 ms
01_0014_0001_c12_ip6_m03.jpg
1106 ms
01_0088_0022_c06_ip6_m03.jpg
1119 ms
collect
19 ms
collect
131 ms
tag
104 ms
118 ms
event
751 ms
conversion_async.js
23 ms
l
672 ms
ga-audiences
53 ms
47 ms
27 ms
23 ms
xd_arbiter.php
264 ms
cs
169 ms
500210.js
929 ms
acs
711 ms
_tag_mobylog.js
181 ms
xd_plugin.js
361 ms
mktr-3c17f8c059068f850662b33256083dcf.js
958 ms
xd_jquery_selectors.js
361 ms
phocase.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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Buttons do not have an accessible name
Links do not have a discernible name
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
phocase.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
phocase.jp SEO score
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 Phocase.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 Phocase.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.
phocase.jp
Open Graph data is detected on the main page of Phocase. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: