Tools & Wizards About Us
suehirogari.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

suehirogari.com

社内SEのウェブ制作 | 情報技術担当者のホームページ

Page Load Speed

5.9 sec in total

First Response

1.7 sec

Resources Loaded

3.9 sec

Page Rendered

338 ms

suehirogari.com screenshot

About Website

Visit suehirogari.com now to see the best up-to-date Suehirogari content for Japan and also check out these interesting facts you probably never knew about suehirogari.com

LINEPOPやラインバブル・まちがい探しやウィンドランナー等の高得点や裏技からフェイスブックやwindowsやoutlookのエラー等。その他企業内SEやウェブ担当者が気にすべき点の備忘録

Visit suehirogari.com

Key Findings

We analyzed Suehirogari.com page load time and found that the first response time was 1.7 sec and then it took 4.2 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

suehirogari.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.0 s

100/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

Network Requests Diagram

suehirogari.com

1691 ms

xoops.css

562 ms

style.css

564 ms

block_style.css

563 ms

xoops.js

573 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 26% of them (29 requests) were addressed to the original Suehirogari.com, 32% (35 requests) were made to I.ytimg.com and 5% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Suehirogari.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.0 kB (18%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Suehirogari.com main page is 1.5 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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 53.5 kB

  • Original 62.8 kB
  • After minification 42.0 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 20.7 kB, which is 33% 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 53.5 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 69 B

  • Original 205.2 kB
  • After minification 205.1 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. Suehirogari images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 109.2 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 940.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

-62%

Potential reduce by 112.3 kB

  • Original 181.6 kB
  • After minification 181.2 kB
  • After compression 69.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. Suehirogari.com needs all CSS files to be minified and compressed as it can save up to 112.3 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (42%)

Requests Now

85

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

suehirogari.com

suehirogari.com

1691 ms

xoops.css

xoops.css

562 ms

style.css

style.css

564 ms

block_style.css

block_style.css

563 ms

xoops.js

xoops.js

573 ms

1.jpg

1.jpg

10 ms

multiswap.js

multiswap.js

572 ms

multiswap.js

multiswap.js

187 ms

rakuten_widget.js

rakuten_widget.js

892 ms

show_ads.js

show_ads.js

70 ms

adsbygoogle.js

adsbygoogle.js

167 ms

nendAdLoader.js

nendAdLoader.js

51 ms

1.jpg

1.jpg

14 ms

1.jpg

1.jpg

10 ms

1.jpg

1.jpg

11 ms

1.jpg

1.jpg

8 ms

0.jpg

0.jpg

93 ms

0.jpg

0.jpg

19 ms

0.jpg

0.jpg

65 ms

0.jpg

0.jpg

164 ms

0.jpg

0.jpg

111 ms

JS163_72A.jpg

JS163_72A.jpg

569 ms

6.jpg

6.jpg

735 ms

3.jpg

3.jpg

736 ms

7.jpg

7.jpg

737 ms

8.jpg

8.jpg

751 ms

16.jpg

16.jpg

752 ms

14.jpg

14.jpg

751 ms

5.jpg

5.jpg

913 ms

11.jpg

11.jpg

914 ms

15.jpg

15.jpg

915 ms

17.jpg

17.jpg

933 ms

4.jpg

4.jpg

935 ms

9.jpg

9.jpg

935 ms

10.jpg

10.jpg

1090 ms

2.jpg

2.jpg

1091 ms

12.jpg

12.jpg

1092 ms

element.js

element.js

42 ms

nendAdLoader.js

nendAdLoader.js

35 ms

ex.css

ex.css

558 ms

1129 ms

header_main_photo.png

header_main_photo.png

188 ms

dot_line_v.gif

dot_line_v.gif

182 ms

2.jpg

2.jpg

12 ms

3.jpg

3.jpg

13 ms

2.jpg

2.jpg

58 ms

3.jpg

3.jpg

58 ms

2.jpg

2.jpg

12 ms

3.jpg

3.jpg

13 ms

2.jpg

2.jpg

32 ms

3.jpg

3.jpg

31 ms

2.jpg

2.jpg

32 ms

3.jpg

3.jpg

33 ms

2.jpg

2.jpg

49 ms

3.jpg

3.jpg

50 ms

1.jpg

1.jpg

38 ms

2.jpg

2.jpg

112 ms

3.jpg

3.jpg

112 ms

1.jpg

1.jpg

133 ms

2.jpg

2.jpg

112 ms

3.jpg

3.jpg

112 ms

1.jpg

1.jpg

112 ms

2.jpg

2.jpg

228 ms

3.jpg

3.jpg

227 ms

1.jpg

1.jpg

226 ms

2.jpg

2.jpg

138 ms

3.jpg

3.jpg

151 ms

1.jpg

1.jpg

159 ms

355 ms

page_top.gif

page_top.gif

195 ms

dot_line.gif

dot_line.gif

196 ms

mw_dynamic_view.html

mw_dynamic_view.html

209 ms

adsbygoogle.js

adsbygoogle.js

155 ms

show_ads_impl.js

show_ads_impl.js

277 ms

ga.js

ga.js

11 ms

widget

widget

68 ms

__utm.gif

__utm.gif

13 ms

collect

collect

25 ms

ga-audiences

ga-audiences

79 ms

embed_loader.js

embed_loader.js

25 ms

dailytrends

dailytrends

146 ms

print.css

print.css

233 ms

pc_pcview_all.css

pc_pcview_all.css

4 ms

front_merged.js

front_merged.js

21 ms

getMWConf.php

getMWConf.php

698 ms

loading.gif

loading.gif

10 ms

buttons.gif

buttons.gif

26 ms

css

css

131 ms

css

css

131 ms

css

css

115 ms

css

css

130 ms

embed_fe_trending_searches_v1_css_bin.css

embed_fe_trending_searches_v1_css_bin.css

115 ms

loader.js

loader.js

113 ms

third_parties_min.js

third_parties_min.js

226 ms

angular-material.min.js

angular-material.min.js

139 ms

icon

icon

196 ms

icon

icon

145 ms

embed_fe_trending_searches_v1_js_bin__ja.js

embed_fe_trending_searches_v1_js_bin__ja.js

256 ms

zrt_lookup.html

zrt_lookup.html

136 ms

ads

ads

517 ms

ads

ads

303 ms

async_survey

async_survey

161 ms

ads

ads

327 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

123 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

127 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

130 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

142 ms

ga.js

ga.js

16 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

7 ms

collect

collect

11 ms

Accessibility Review

suehirogari.com accessibility score

81

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

suehirogari.com best practices score

67

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

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

suehirogari.com SEO score

62

Search Engine Optimization Advices

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Suehirogari.com 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 Suehirogari.com 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

suehirogari.com

Open Graph description is not detected on the main page of Suehirogari. 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: