Tools & Wizards About Us
some-day.jp screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

some-day.jp

緑区・刈谷の美容室SOMEDAY［サムデイ］ | Just another WordPress site

Page Load Speed

7.6 sec in total

First Response

831 ms

Resources Loaded

5.5 sec

Page Rendered

1.2 sec

some-day.jp screenshot

About Website

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.jp

Key Findings

We analyzed Some-day.jp page load time and found that the first response time was 831 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.

Performance Metrics

some-day.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.223

56/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

Network Requests Diagram

www.some-day.jp

831 ms

plugins.min.css

194 ms

style.css

564 ms

slick-theme.min.css

48 ms

slick.min.css

44 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 61% of them (48 requests) were addressed to the original Some-day.jp, 11% (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 (3.3 sec) belongs to the original domain Some-day.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.0 kB (1%)

Content Size

16.8 MB

After Optimization

16.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Some-day.jp main page is 16.8 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. 75% 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 16.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 54.6 kB

  • Original 61.9 kB
  • After minification 55.5 kB
  • After compression 7.4 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 54.6 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 22.7 kB

  • Original 16.4 MB
  • After minification 16.4 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. Some Day images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.3 kB

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

CSS Optimization

-21%

Potential reduce by 5.4 kB

  • Original 25.6 kB
  • After minification 25.6 kB
  • After compression 20.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. Some-day.jp needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (43%)

Requests Now

74

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 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.

Network Requests Diagram

www.some-day.jp

www.some-day.jp

831 ms

plugins.min.css

plugins.min.css

194 ms

style.css

style.css

564 ms

slick-theme.min.css

slick-theme.min.css

48 ms

slick.min.css

slick.min.css

44 ms

css

css

46 ms

css

css

62 ms

js

js

74 ms

jquery.min.js

jquery.min.js

28 ms

main.js

main.js

371 ms

common.js

common.js

385 ms

slick.min.js

slick.min.js

49 ms

jquery.matchHeight.js

jquery.matchHeight.js

379 ms

insta.js

insta.js

381 ms

css

css

20 ms

js

js

90 ms

analytics.js

analytics.js

85 ms

logo.svg

logo.svg

256 ms

insta.svg

insta.svg

251 ms

menu.svg

menu.svg

251 ms

ph_main.png

ph_main.png

1863 ms

bg01.png

bg01.png

3273 ms

img01.png

img01.png

1270 ms

304-440x440.jpg

304-440x440.jpg

619 ms

301-440x440.jpg

301-440x440.jpg

622 ms

302-440x440.jpg

302-440x440.jpg

437 ms

292-440x440.jpg

292-440x440.jpg

810 ms

290-440x440.jpg

290-440x440.jpg

1003 ms

triangle.svg

triangle.svg

808 ms

arrow_right_wht.svg

arrow_right_wht.svg

995 ms

304-1024x576.jpg

304-1024x576.jpg

1185 ms

301-1024x576.jpg

301-1024x576.jpg

1368 ms

302-1024x914.jpg

302-1024x914.jpg

1196 ms

292-726x1024.jpg

292-726x1024.jpg

1559 ms

290-1003x1024.jpg

290-1003x1024.jpg

1772 ms

bg02.png

bg02.png

1817 ms

img03.png

img03.png

1925 ms

img04.png

img04.png

1748 ms

img05.png

img05.png

2124 ms

img06.png

img06.png

1966 ms

img07.png

img07.png

1999 ms

img13.png

img13.png

2048 ms

img09.png

img09.png

2301 ms

bnr_news03_04.png

bnr_news03_04.png

2159 ms

ico_close.svg

ico_close.svg

2181 ms

bnr_news04.png

bnr_news04.png

2236 ms

bnr_news05.png

bnr_news05.png

2311 ms

img10.png

img10.png

2351 ms

img11.png

img11.png

2361 ms

img12.png

img12.png

2422 ms

img_footer_someday.jpg

img_footer_someday.jpg

2488 ms

img_footer_lx.jpg

img_footer_lx.jpg

2499 ms

img_footer_aile.jpg

img_footer_aile.jpg

2555 ms

ajax-loader.gif

ajax-loader.gif

78 ms

embed

embed

218 ms

181 ms

linkid.js

linkid.js

35 ms

collect

collect

37 ms

slick.woff

slick.woff

19 ms

cocogooseletterpress-trial.woff

cocogooseletterpress-trial.woff

2301 ms

slick.woff

slick.woff

2362 ms

arrow_top.svg

arrow_top.svg

2428 ms

collect

collect

28 ms

collect

collect

40 ms

js

js

44 ms

rs=ABFko3_Sq0wVhrerNQIOGZ8t9QLH3ZLPYw

rs=ABFko3_Sq0wVhrerNQIOGZ8t9QLH3ZLPYw

58 ms

m=embed

m=embed

15 ms

client.js

client.js

19 ms

arrow_left.svg

arrow_left.svg

2253 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

logo-plus.png

logo-plus.png

29 ms

googlelogo_color_46x16dp.png

googlelogo_color_46x16dp.png

34 ms

blank.gif

blank.gif

10 ms

menu_arrow_open.gif

menu_arrow_open.gif

5 ms

icon_print.gif

icon_print.gif

10 ms

btn_menu6.gif

btn_menu6.gif

15 ms

combined_v22.png

combined_v22.png

14 ms

events

events

215 ms

arrow_right.svg

arrow_right.svg

2110 ms

Accessibility Review

some-day.jp accessibility score

58

Accessibility Issues

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

High

[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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

some-day.jp best practices score

75

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

some-day.jp SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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 doesn't use 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 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.

Social Sharing Optimization

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: