Tools & Wizards About Us
wpblog.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    49% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 93% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

wpblog.jp

クラウド型高速レンタルサーバー【スターサーバー】

Page Load Speed

6.1 sec in total

First Response

578 ms

Resources Loaded

5.2 sec

Page Rendered

332 ms

wpblog.jp screenshot

About Website

Welcome to wpblog.jp homepage info - get ready to check Wpblog best content for Japan right away, or after learning these important things about wpblog.jp

レンタルサーバーの【スターサーバー】は、高速・格安のクラウド型レンタルサーバーです。オールSSD＆nginx(エンジンエックス)を搭載した高速サーバー環境が月額138円(税込)から利用可能で、WordPressなどのCMSやWebサイトが快適に動作する環境を提供します。

Visit wpblog.jp

Key Findings

We analyzed Wpblog.jp page load time and found that the first response time was 578 ms and then it took 5.6 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

wpblog.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value390 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.635

9/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

wpblog.jp

578 ms

www.wpblog.jp

732 ms

base.css

346 ms

layout.css

349 ms

jquery.js

851 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 71% of them (70 requests) were addressed to the original Wpblog.jp, 26% (25 requests) were made to Secure.netowl.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Wpblog.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.8 kB (29%)

Content Size

389.8 kB

After Optimization

275.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wpblog.jp main page is 389.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. 20% of websites need less resources to load. Images take 212.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 27.3 kB

  • Original 33.4 kB
  • After minification 25.4 kB
  • After compression 6.2 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 8.0 kB, which is 24% 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 27.3 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 1.1 kB

  • Original 212.8 kB
  • After minification 211.7 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. Wpblog images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 61.0 kB

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

CSS Optimization

-83%

Potential reduce by 25.4 kB

  • Original 30.6 kB
  • After minification 22.4 kB
  • After compression 5.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. Wpblog.jp needs all CSS files to be minified and compressed as it can save up to 25.4 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

95

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wpblog.jp

wpblog.jp

578 ms

www.wpblog.jp

www.wpblog.jp

732 ms

base.css

base.css

346 ms

layout.css

layout.css

349 ms

jquery.js

jquery.js

851 ms

jquery.rollover.js

jquery.rollover.js

341 ms

smartRollover.js

smartRollover.js

343 ms

smooth.pack.js

smooth.pack.js

345 ms

viewCurrent.js

viewCurrent.js

502 ms

google.js

google.js

509 ms

netowlheader.js

netowlheader.js

1571 ms

analytics.js

analytics.js

19 ms

collect

collect

41 ms

collect

collect

62 ms

netowlheader.css

netowlheader.css

186 ms

header_logo.png

header_logo.png

178 ms

logo_netowl.png

logo_netowl.png

189 ms

ttl_domain.png

ttl_domain.png

369 ms

logo_stardomain.png

logo_stardomain.png

499 ms

label_campaign.png

label_campaign.png

514 ms

ttl_retalserver.png

ttl_retalserver.png

513 ms

logo_webcrow.png

logo_webcrow.png

545 ms

logo_minibird.png

logo_minibird.png

551 ms

logo_firebird.png

logo_firebird.png

554 ms

logo_clouver.png

logo_clouver.png

662 ms

ttl_ssl.png

ttl_ssl.png

679 ms

logo_sslbox.png

logo_sslbox.png

679 ms

ttl_wordpress.png

ttl_wordpress.png

723 ms

logo_wpblog.png

logo_wpblog.png

733 ms

ttl_app.png

ttl_app.png

737 ms

logo_imgtalk.png

logo_imgtalk.png

825 ms

balloon_arrow.png

balloon_arrow.png

847 ms

bg.png

bg.png

847 ms

ico_menu.png

ico_menu.png

903 ms

ico_pencil.png

ico_pencil.png

915 ms

bg_border_dotted.png

bg_border_dotted.png

919 ms

ico_info.png

ico_info.png

988 ms

ico_person.png

ico_person.png

1019 ms

ico_lock.png

ico_lock.png

1019 ms

main_navi_home.png

main_navi_home.png

174 ms

main_navi_application.png

main_navi_application.png

172 ms

main_navi_support.png

main_navi_support.png

174 ms

main_navi_news.png

main_navi_news.png

176 ms

login_button.png

login_button.png

175 ms

top_img.png

top_img.png

976 ms

top_feature_title.png

top_feature_title.png

340 ms

top_feature_list_title_01.png

top_feature_list_title_01.png

343 ms

top_feature_list_img_01.png

top_feature_list_img_01.png

511 ms

top_feature_list_title_02.png

top_feature_list_title_02.png

343 ms

top_feature_list_img_02.png

top_feature_list_img_02.png

518 ms

top_feature_list_title_03.png

top_feature_list_title_03.png

510 ms

top_feature_list_img_03.png

top_feature_list_img_03.png

683 ms

top_feature_list_title_04.png

top_feature_list_title_04.png

513 ms

top_feature_list_img_04.png

top_feature_list_img_04.png

680 ms

top_feature_list_title_05.png

top_feature_list_title_05.png

680 ms

top_feature_list_img_05.png

top_feature_list_img_05.png

851 ms

top_feature_list_title_06.png

top_feature_list_title_06.png

687 ms

top_feature_list_img_06.png

top_feature_list_img_06.png

849 ms

service_image_list_01.png

service_image_list_01.png

1019 ms

service_image_list_02.png

service_image_list_02.png

1020 ms

service_image_list_03.png

service_image_list_03.png

859 ms

service_image_list_04.png

service_image_list_04.png

1188 ms

upper_plan_pr_title.png

upper_plan_pr_title.png

1021 ms

upper_plan_pr_main_copy.png

upper_plan_pr_main_copy.png

1031 ms

upper_plan_pr_main_img.png

upper_plan_pr_main_img.png

1146 ms

upper_plan_link_button_off.png

upper_plan_link_button_off.png

1188 ms

main_h3_back.png

main_h3_back.png

1190 ms

main_news_title.png

main_news_title.png

1190 ms

dot_line_x.gif

dot_line_x.gif

1205 ms

common_application_button_off.png

common_application_button_off.png

1497 ms

stardomain_pr_banner.png

stardomain_pr_banner.png

1695 ms

sub_application_banner.png

sub_application_banner.png

1357 ms

sub_contents_upper_plan_banner.png

sub_contents_upper_plan_banner.png

1529 ms

sub_section_bottom_back.png

sub_section_bottom_back.png

1359 ms

sub_section_title_back.png

sub_section_title_back.png

1291 ms

sub_section_marker_gray.png

sub_section_marker_gray.png

1369 ms

side_qabbs_banner.png

side_qabbs_banner.png

1541 ms

stardomain_banner.png

stardomain_banner.png

1386 ms

campaign_marker.png

campaign_marker.png

1509 ms

white_arrow_marker.png

white_arrow_marker.png

1535 ms

footer_pagetop_button_off.png

footer_pagetop_button_off.png

1373 ms

footer_logo.png

footer_logo.png

1388 ms

footer_service_list_icon_webcrow.png

footer_service_list_icon_webcrow.png

1516 ms

footer_service_list_icon_minibird.png

footer_service_list_icon_minibird.png

1364 ms

footer_service_list_icon_firebird.png

footer_service_list_icon_firebird.png

1370 ms

footer_service_list_icon_clouver.png

footer_service_list_icon_clouver.png

1367 ms

footer_service_list_icon_stardomain.png

footer_service_list_icon_stardomain.png

1363 ms

footer_service_list_icon_sslbox.png

footer_service_list_icon_sslbox.png

1223 ms

footer_service_list_icon_wpblog.png

footer_service_list_icon_wpblog.png

1355 ms

footer_service_list_icon_freewiki.png

footer_service_list_icon_freewiki.png

1360 ms

footer_service_list_icon_analyzer.png

footer_service_list_icon_analyzer.png

1361 ms

footer_service_list_icon_mailform.png

footer_service_list_icon_mailform.png

1200 ms

footer_service_list_icon_shopstar.png

footer_service_list_icon_shopstar.png

1197 ms

footer_service_list_icon_imgtalk.png

footer_service_list_icon_imgtalk.png

1214 ms

main_navi_home_hover.png

main_navi_home_hover.png

1240 ms

main_navi_application_hover.png

main_navi_application_hover.png

1193 ms

main_navi_support_hover.png

main_navi_support_hover.png

1198 ms

main_navi_news_hover.png

main_navi_news_hover.png

1198 ms

Accessibility Review

wpblog.jp accessibility score

97

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.

Best Practices

wpblog.jp best practices score

83

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

SEO Factors

wpblog.jp SEO score

92

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

    EUC-JP

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

wpblog.jp

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