Tools & Wizards About Us
ls-g.co.jp screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

ls-g.co.jp

神奈川県の浴室リフォーム、分譲マンションリフォームはLSコーポレーションで！

Page Load Speed

9.7 sec in total

First Response

552 ms

Resources Loaded

8.9 sec

Page Rendered

230 ms

ls-g.co.jp screenshot

About Website

Visit ls-g.co.jp now to see the best up-to-date Ls G content and also check out these interesting facts you probably never knew about ls-g.co.jp

浴室リフォーム（ユニットバスリフォーム）、トイレやキッチン、給湯器などの水まわりリフォームは株式会社LSコーポレーションにおまかせください！私たちは神奈川県の分譲マンションリフォーム専門店です。横浜市、川崎市、相模原市など、神奈川全域に対応しています。

Visit ls-g.co.jp

Key Findings

We analyzed Ls-g.co.jp page load time and found that the first response time was 552 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

ls-g.co.jp performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value19.7 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.519

15/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

ls-g.co.jp

552 ms

www.ls-g.co.jp

766 ms

import.css

380 ms

dw_common.js

377 ms

JUDGE.JS

377 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 85% of them (90 requests) were addressed to the original Ls-g.co.jp, 11% (12 requests) were made to Static.xx.fbcdn.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Ls-g.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.6 kB (3%)

Content Size

1.2 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ls-g.co.jp main page is 1.2 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 16.1 kB

  • Original 22.4 kB
  • After minification 20.7 kB
  • After compression 6.3 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 16.1 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 20.2 kB

  • Original 1.2 MB
  • After minification 1.2 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. Ls G images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 399 B

  • Original 19.4 kB
  • After minification 19.4 kB
  • After compression 19.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

-17%

Potential reduce by 854 B

  • Original 5.1 kB
  • After minification 5.1 kB
  • After compression 4.3 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. Ls-g.co.jp needs all CSS files to be minified and compressed as it can save up to 854 B or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (25%)

Requests Now

104

After Optimization

78

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ls G. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ls-g.co.jp

ls-g.co.jp

552 ms

www.ls-g.co.jp

www.ls-g.co.jp

766 ms

import.css

import.css

380 ms

dw_common.js

dw_common.js

377 ms

JUDGE.JS

JUDGE.JS

377 ms

ie7_flash.js

ie7_flash.js

384 ms

content.css

content.css

367 ms

base.css

base.css

372 ms

top.css

top.css

375 ms

form.css

form.css

387 ms

ga.js

ga.js

56 ms

bg_body.jpg

bg_body.jpg

210 ms

bg_body_bottom.jpg

bg_body_bottom.jpg

755 ms

bg_h1.gif

bg_h1.gif

378 ms

logo.jpg

logo.jpg

568 ms

h_txt.gif

h_txt.gif

408 ms

h_phone.jpg

h_phone.jpg

596 ms

top_mv.jpg

top_mv.jpg

1375 ms

g_bnr01.jpg

g_bnr01.jpg

1135 ms

gNav03.jpg

gNav03.jpg

761 ms

gNav04.jpg

gNav04.jpg

974 ms

gNav05.jpg

gNav05.jpg

986 ms

gNav06.jpg

gNav06.jpg

1260 ms

gNav07.jpg

gNav07.jpg

1142 ms

gNav14.jpg

gNav14.jpg

1539 ms

gNav08.jpg

gNav08.jpg

1370 ms

gNav09.jpg

gNav09.jpg

1501 ms

g_bnr18.gif

g_bnr18.gif

1511 ms

gNav13.jpg

gNav13.jpg

1826 ms

gNav01.jpg

gNav01.jpg

1770 ms

bg_bnr.gif

bg_bnr.gif

1750 ms

bg_bnr_top.gif

bg_bnr_top.gif

1870 ms

g_bnr03.jpg

g_bnr03.jpg

1878 ms

g_bnr02.jpg

g_bnr02.jpg

1918 ms

g_bnr15.jpg

g_bnr15.jpg

2178 ms

g_bnr08.jpg

g_bnr08.jpg

2158 ms

g_bnr04.jpg

g_bnr04.jpg

2216 ms

g_bnr10.jpg

g_bnr10.jpg

2244 ms

g_bnr12.jpg

g_bnr12.jpg

2260 ms

g_bnr16.jpg

g_bnr16.jpg

2287 ms

g_bnr13.jpg

g_bnr13.jpg

2535 ms

g_bnr14.jpg

g_bnr14.jpg

2546 ms

bg_bnr_bottom.gif

bg_bnr_bottom.gif

2590 ms

g_bnr05.jpg

g_bnr05.jpg

2794 ms

g_bnr19.gif

g_bnr19.gif

2637 ms

bnr01.jpg

bnr01.jpg

2661 ms

bnr02.jpg

bnr02.jpg

2874 ms

likebox.php

likebox.php

181 ms

__utm.gif

__utm.gif

11 ms

bnr03.jpg

bnr03.jpg

2732 ms

YSVNzQMiK3c.css

YSVNzQMiK3c.css

17 ms

XVfyC-hY3iC.js

XVfyC-hY3iC.js

23 ms

4vv_Lf70fZS.js

4vv_Lf70fZS.js

51 ms

8O2J-mJIMh1.js

8O2J-mJIMh1.js

52 ms

Y4lQlibYsna.js

Y4lQlibYsna.js

54 ms

4aFcRp6-srT.js

4aFcRp6-srT.js

56 ms

Mgao39tvtRW.js

Mgao39tvtRW.js

54 ms

mtuC5ESzCwN.js

mtuC5ESzCwN.js

52 ms

HYZXJ6lnRqE.js

HYZXJ6lnRqE.js

52 ms

p55HfXW__mM.js

p55HfXW__mM.js

52 ms

300477064_751042999572569_2929776796264994233_n.jpg

300477064_751042999572569_2929776796264994233_n.jpg

106 ms

mFWyxjCB51c.js

mFWyxjCB51c.js

10 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

9 ms

bnr04.jpg

bnr04.jpg

2604 ms

bg_contents.jpg

bg_contents.jpg

2736 ms

n_title.gif

n_title.gif

2480 ms

bnr_campaign.jpg

bnr_campaign.jpg

3106 ms

s_title01.jpg

s_title01.jpg

2530 ms

photo01.jpg

photo01.jpg

2948 ms

s_title02.jpg

s_title02.jpg

2396 ms

photo02.jpg

photo02.jpg

2810 ms

s_title03.jpg

s_title03.jpg

2374 ms

photo03.jpg

photo03.jpg

2888 ms

s_title04.jpg

s_title04.jpg

2486 ms

photo04.jpg

photo04.jpg

2703 ms

s_title05.jpg

s_title05.jpg

2873 ms

photo05.jpg

photo05.jpg

3123 ms

s_title06.jpg

s_title06.jpg

2777 ms

photo06.jpg

photo06.jpg

3197 ms

bg_contact.gif

bg_contact.gif

2654 ms

bg_contact_bottom.gif

bg_contact_bottom.gif

2688 ms

bg_contact_top.gif

bg_contact_top.gif

2806 ms

contact.jpg

contact.jpg

3190 ms

area_map.gif

area_map.gif

2908 ms

contact_logo.jpg

contact_logo.jpg

2935 ms

bg_fNav.gif

bg_fNav.gif

2844 ms

btn_flash.jpg

btn_flash.jpg

2828 ms

g_bnr01_ro.jpg

g_bnr01_ro.jpg

555 ms

photo01_ro.jpg

photo01_ro.jpg

734 ms

photo02_ro.jpg

photo02_ro.jpg

734 ms

photo03_ro.jpg

photo03_ro.jpg

752 ms

photo04_ro.jpg

photo04_ro.jpg

379 ms

contact_ro.jpg

contact_ro.jpg

777 ms

n_title_ro.gif

n_title_ro.gif

758 ms

gNav01_ro.jpg

gNav01_ro.jpg

946 ms

gNav02_ro.jpg

gNav02_ro.jpg

1104 ms

gNav04_ro.jpg

gNav04_ro.jpg

1102 ms

gNav05_ro.jpg

gNav05_ro.jpg

1117 ms

gNav06_ro.jpg

gNav06_ro.jpg

1148 ms

gNav07_ro.jpg

gNav07_ro.jpg

1156 ms

gNav08_ro.jpg

gNav08_ro.jpg

1328 ms

gNav09_ro.jpg

gNav09_ro.jpg

1470 ms

gNav10_ro.jpg

gNav10_ro.jpg

1466 ms

gNav11_ro.jpg

gNav11_ro.jpg

1505 ms

g_bnr17_ro.gif

g_bnr17_ro.gif

1519 ms

g_bnr18_ro.gif

g_bnr18_ro.gif

1538 ms

Accessibility Review

ls-g.co.jp accessibility score

65

Accessibility Issues

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.

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

<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

Best Practices

ls-g.co.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

ls-g.co.jp SEO score

58

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ls-g.co.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 Ls-g.co.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ls-g.co.jp

Open Graph description is not detected on the main page of Ls G. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: