14.3 sec in total
658 ms
5 sec
8.6 sec
Click here to check amazing Some Day content. Otherwise, check out these important facts you probably never knew about some-day.jp
緑区・刈谷で美容室を運営するSOMEDAY[サムデイ]です。サムデイであなたももっと可愛くなりませんか?髪のお悩みをお持ちの方は気軽にスタッフまで!HPではお得なクーポンやスタッフ情報が掲載されていますので、是非ご覧下さい。
Visit some-day.jpWe analyzed Some-day.jp page load time and found that the first response time was 658 ms and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
some-day.jp performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value10.9 s
0/100
25%
Value11.5 s
5/100
10%
Value390 ms
69/100
30%
Value0.226
55/100
15%
Value20.1 s
2/100
10%
658 ms
187 ms
541 ms
83 ms
96 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 59% of them (46 requests) were addressed to the original Some-day.jp, 12% (9 requests) were made to Calendar.google.com and 6% (5 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Some-day.jp.
Page size can be reduced by 86.3 kB (1%)
16.0 MB
16.0 MB
In fact, the total size of Some-day.jp main page is 16.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. 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 15.9 MB which makes up the majority of the site volume.
Potential reduce by 50.5 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 6.5 kB, which is 11% 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 50.5 kB or 87% of the original size.
Potential reduce by 27.9 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. Some Day images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 5.5 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. Some-day.jp needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 18% of the original size.
Number of requests can be reduced by 33 (45%)
73
40
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Some Day. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.some-day.jp
658 ms
plugins.min.css
187 ms
style.css
541 ms
slick-theme.min.css
83 ms
slick.min.css
96 ms
css
97 ms
css
128 ms
js
101 ms
jquery.min.js
65 ms
main.js
366 ms
common.js
374 ms
slick.min.js
77 ms
jquery.matchHeight.js
382 ms
insta.js
378 ms
css
32 ms
analytics.js
287 ms
logo.svg
281 ms
insta.svg
457 ms
menu.svg
461 ms
ph_main.png
1982 ms
bg01.png
1853 ms
img01.png
2224 ms
9C7C0C18-E876-4090-BD00-E21A5FE9AE09-440x440.jpeg
468 ms
86C51BDC-42C2-471C-8982-345157364EE8-435x440.jpeg
555 ms
noImage03.jpg
923 ms
68A9BFC6-284A-47D1-B16B-FA4490490C52-440x440.jpeg
613 ms
triangle.svg
728 ms
arrow_right_wht.svg
749 ms
9C7C0C18-E876-4090-BD00-E21A5FE9AE09.jpeg
1308 ms
86C51BDC-42C2-471C-8982-345157364EE8.jpeg
925 ms
noImage01.jpg
1099 ms
68A9BFC6-284A-47D1-B16B-FA4490490C52-565x1024.jpeg
1101 ms
bg02.png
2567 ms
img03.png
2030 ms
img04.png
1620 ms
img05.png
2152 ms
img06.png
2030 ms
img07.png
2146 ms
img13.png
2381 ms
img09.png
2214 ms
bnr_news03_02.png
2326 ms
ico_close.svg
2329 ms
bnr_news04.png
2395 ms
bnr_news05.png
2395 ms
img10.png
2505 ms
img11.png
2508 ms
img12.png
2562 ms
img_footer_someday.jpg
2572 ms
img_footer_lx.jpg
2575 ms
img_footer_aile.jpg
2686 ms
arrow_top.svg
2688 ms
cocogooseletterpress-trial.woff
2532 ms
ajax-loader.gif
198 ms
arrow_left.svg
2307 ms
embed
359 ms
arrow_right.svg
2342 ms
158 ms
linkid.js
67 ms
collect
50 ms
slick.woff
36 ms
slick.woff
2286 ms
collect
41 ms
collect
73 ms
1a56b687b1b00b90b74491e93879cfc6embedcompiled_fastui.css
16 ms
m=embed
340 ms
client.js
45 ms
cb=gapi.loaded_0
8 ms
logo-plus.png
50 ms
googlelogo_color_46x16dp.png
60 ms
blank.gif
11 ms
menu_arrow_open.gif
11 ms
icon_print.gif
14 ms
btn_menu6.gif
16 ms
combined_v22.png
14 ms
proxy.html
31 ms
googleapis.proxy.js
12 ms
cb=gapi.loaded_0
9 ms
events
125 ms
some-day.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-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
some-day.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
some-day.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Some-day.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 Some-day.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.
some-day.jp
Open Graph data is detected on the main page of Some Day. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: