Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

sitelife.jp

京都 美容室 ヘアサロン LIFE / LIFE ADORE ライフ / ライフアドア | LIFE / LIFE ADORE

Page Load Speed

6.5 sec in total

First Response

1.7 sec

Resources Loaded

4.8 sec

Page Rendered

74 ms

sitelife.jp screenshot

About Website

Welcome to sitelife.jp homepage info - get ready to check Site LIFE best content right away, or after learning these important things about sitelife.jp

京都のヘアサロン、美容室のLIFE / LIFE ADORE ライフ / ライフアドアのオフィシャルサイトです。烏丸紫明と烏丸三条の店舗のご案内やメニューやプライス、スタッフ紹介などをご覧頂けます。ご来店頂ける皆様をお待ちしております。

Visit sitelife.jp

Key Findings

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

Performance Metrics

sitelife.jp performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

sitelife.jp

1691 ms

www.sitelife.jp

2345 ms

js

71 ms

ZXhwb3J0cy5sb2FkQ1NTPW46ZS5sb2FkQ1NTPW59KCJ1bmRlZmluZWQiIT10eXBlb2YgZ2xvYmFsP2dsb2JhbDp0aGlzKTs=

5 ms

1722452680-css28fba9ff5e8d6e1b59a549c22f64c290f3d141085bf7f6daf796e2f4dc011.css

176 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 69% of them (11 requests) were addressed to the original Sitelife.jp, 25% (4 requests) were made to and 6% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Sitelife.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.3 kB (17%)

Content Size

142.8 kB

After Optimization

118.5 kB

In fact, the total size of Sitelife.jp main page is 142.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 82.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 23.8 kB

  • Original 32.9 kB
  • After minification 32.9 kB
  • After compression 9.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. 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 23.8 kB or 72% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 82.0 kB
  • After minification 82.0 kB
  • After compression 82.0 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

-2%

Potential reduce by 537 B

  • Original 28.0 kB
  • After minification 27.9 kB
  • After compression 27.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. Sitelife.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (50%)

Requests Now

10

After Optimization

5

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

Accessibility Review

sitelife.jp accessibility score

97

Accessibility Issues

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

Links do not have a discernible name

Best Practices

sitelife.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

sitelife.jp SEO score

93

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

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 uses legible font sizes

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

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