Tools & Wizards About Us
seopitshu.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

seopitshu.jp

SEO！検索順位アップの方法を30分で解説(初心者向け)｜SEOピッシュ

Page Load Speed

9.3 sec in total

First Response

1.1 sec

Resources Loaded

6.6 sec

Page Rendered

1.6 sec

seopitshu.jp screenshot

About Website

Visit seopitshu.jp now to see the best up-to-date SEO Pitshu content for Japan and also check out these interesting facts you probably never knew about seopitshu.jp

自分でSEO対策をするなら知っておくべき「内部SEO」・「外部SEO」・「SXO（閲覧者評価）」を初心者向けに解説します。SEO対策の３大要素を中心に、30分の流し読みであなたに必要なSEO対策を紹介します。

Visit seopitshu.jp

Key Findings

We analyzed Seopitshu.jp page load time and found that the first response time was 1.1 sec and then it took 8.2 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

seopitshu.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value5,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

seopitshu.jp

1077 ms

style.css

504 ms

base.css

694 ms

aside.css

702 ms

meanmenu.css

364 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 58% of them (57 requests) were addressed to the original Seopitshu.jp, 8% (8 requests) were made to Fonts.gstatic.com and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Seopitshu.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 307.6 kB (19%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Seopitshu.jp main page is 1.6 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. 85% 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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 42.8 kB

  • Original 57.8 kB
  • After minification 54.1 kB
  • After compression 15.0 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 42.8 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 30.7 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. SEO Pitshu images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 186.3 kB

  • Original 266.7 kB
  • After minification 238.8 kB
  • After compression 80.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 186.3 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 47.7 kB

  • Original 57.7 kB
  • After minification 43.6 kB
  • After compression 10.1 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. Seopitshu.jp needs all CSS files to be minified and compressed as it can save up to 47.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (40%)

Requests Now

88

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

seopitshu.jp

seopitshu.jp

1077 ms

style.css

style.css

504 ms

base.css

base.css

694 ms

aside.css

aside.css

702 ms

meanmenu.css

meanmenu.css

364 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

1142 ms

jquery.meanmenu.min.js

jquery.meanmenu.min.js

715 ms

jquery.socialbutton-1.9.1.min.js

jquery.socialbutton-1.9.1.min.js

889 ms

common.js

common.js

832 ms

root.css

root.css

1029 ms

article.css

article.css

1309 ms

adsbygoogle.js

adsbygoogle.js

4 ms

notosansjapanese.css

notosansjapanese.css

22 ms

analytics.js

analytics.js

18 ms

logo_site.png

logo_site.png

385 ms

root_seotheory_img1.jpg

root_seotheory_img1.jpg

907 ms

root_seotheory_img2.jpg

root_seotheory_img2.jpg

896 ms

root_seotheory_img3.jpg

root_seotheory_img3.jpg

895 ms

root_seotheory_img4.jpg

root_seotheory_img4.jpg

1275 ms

root_attractplan_catch0.png

root_attractplan_catch0.png

1172 ms

root_attractplan_catch1.png

root_attractplan_catch1.png

1213 ms

root_attractplan_catch2.png

root_attractplan_catch2.png

1689 ms

root_attractplan_catch3.png

root_attractplan_catch3.png

2059 ms

root_attractplan_catch4.png

root_attractplan_catch4.png

1775 ms

quarterlyseo_image.png

quarterlyseo_image.png

2399 ms

collect

collect

152 ms

collect

collect

168 ms

ca-pub-3079137949100357.js

ca-pub-3079137949100357.js

178 ms

zrt_lookup.html

zrt_lookup.html

178 ms

show_ads_impl.js

show_ads_impl.js

118 ms

root_seotheory_title_bg.png

root_seotheory_title_bg.png

2675 ms

root_seotheory_title_man.png

root_seotheory_title_man.png

1942 ms

icon_free.png

icon_free.png

1988 ms

icon_seotool_no1.png

icon_seotool_no1.png

2137 ms

icon_seotool_ranking.png

icon_seotool_ranking.png

2369 ms

icon_seotool_pageassess.png

icon_seotool_pageassess.png

2443 ms

icon_seotool_siteassess.png

icon_seotool_siteassess.png

2531 ms

icon_seotool_contentssup.png

icon_seotool_contentssup.png

2701 ms

icon_seotool_occur.png

icon_seotool_occur.png

2735 ms

icon_seoparts_premierlink.png

icon_seoparts_premierlink.png

2704 ms

icon_seoparts_googleimpact.png

icon_seoparts_googleimpact.png

2807 ms

icon_seoparts_yahooimpact.png

icon_seoparts_yahooimpact.png

2859 ms

icon_seoparts_bannerbuild.png

icon_seoparts_bannerbuild.png

3007 ms

icon_seoparts_dailyranking.png

icon_seoparts_dailyranking.png

3020 ms

icon_book.png

icon_book.png

3218 ms

icon_seoseminar_01.png

icon_seoseminar_01.png

3069 ms

icon_seoseminar_02.png

icon_seoseminar_02.png

3146 ms

icon_seoseminar_03.png

icon_seoseminar_03.png

3224 ms

icon_seoseminar_04.png

icon_seoseminar_04.png

3325 ms

icon_seoseminar_05.png

icon_seoseminar_05.png

3396 ms

icon_seoseminar_06.png

icon_seoseminar_06.png

3461 ms

icon_seoseminar_07.png

icon_seoseminar_07.png

3484 ms

icon_seoseminar_08.png

icon_seoseminar_08.png

3553 ms

quarterlyseo_catch.png

quarterlyseo_catch.png

4345 ms

icomoon.woff

icomoon.woff

3961 ms

NotoSansJP-Bold.woff

NotoSansJP-Bold.woff

196 ms

NotoSansJP-Black.woff

NotoSansJP-Black.woff

329 ms

NotoSansJP-Medium.woff

NotoSansJP-Medium.woff

345 ms

NotoSansJP-Regular.woff

NotoSansJP-Regular.woff

333 ms

NotoSansJP-DemiLight.woff

NotoSansJP-DemiLight.woff

343 ms

NotoSansJP-Light.woff

NotoSansJP-Light.woff

332 ms

NotoSansJP-Thin.woff

NotoSansJP-Thin.woff

329 ms

widgets.js

widgets.js

100 ms

plusone.js

plusone.js

124 ms

button-only.gif

button-only.gif

603 ms

bookmark_button.js

bookmark_button.js

616 ms

noteit.js

noteit.js

102 ms

article-clipper-vert.png

article-clipper-vert.png

90 ms

ga-audiences

ga-audiences

116 ms

ads

ads

519 ms

like.php

like.php

194 ms

osd.js

osd.js

23 ms

searchengine_signal.png

searchengine_signal.png

3590 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

139 ms

fastbutton

fastbutton

166 ms

wy1X4hBW7e7.js

wy1X4hBW7e7.js

605 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

672 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

302 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

303 ms

postmessageRelay

postmessageRelay

80 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

44 ms

icon_google.png

icon_google.png

3375 ms

searchengine_attention.png

searchengine_attention.png

3178 ms

381 ms

icon_yahoo.png

icon_yahoo.png

3409 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

26 ms

rpc:shindig_random.js

rpc:shindig_random.js

29 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

inquirydesk_girl.png

inquirydesk_girl.png

3324 ms

inquirydesk_faq.png

inquirydesk_faq.png

3190 ms

icon_panda.png

icon_panda.png

3262 ms

reset.css

reset.css

9 ms

entry-button.css

entry-button.css

11 ms

vbutton-bg.png

vbutton-bg.png

4 ms

icon_penguin.png

icon_penguin.png

2902 ms

icon_hummingbird.png

icon_hummingbird.png

2924 ms

icon_gobosei.png

icon_gobosei.png

2694 ms

Accessibility Review

seopitshu.jp accessibility score

72

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-*] attributes do not match their roles

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

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

seopitshu.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

seopitshu.jp SEO score

90

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

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

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

seopitshu.jp

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