Tools & Wizards About Us
55w.jp screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

55w.jp

合同会社ゴーゴーウェブマーケット｜能代市のホームページ制作会社 - ゴーゴーウェブマーケットは、インターネットの活用によって地方生活をより楽しく豊かにすることを目的とした創造＆研究実践チームです。 ホームページ制作やネットショップ支援、ローカル情報サイトや伝統工芸の販売支援など地域にしかない資源を有...

Page Load Speed

15 sec in total

First Response

1.7 sec

Resources Loaded

12.8 sec

Page Rendered

450 ms

55w.jp screenshot

About Website

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

ゴーゴーウェブマーケットは、インターネットの活用によって地方生活をより楽しく豊かにすることを目的とした創造＆研究実践チームです。 ホームページ制作やネットショップ支援、ローカル情報サイトや伝統工芸の販売支援など地域にしかない資源を有効活用し、地方の元気を目指して参ります。

Visit 55w.jp

Key Findings

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

Performance Metrics

55w.jp performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value18.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,880 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.627

9/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

www.55w.jp

1715 ms

normalize.css

184 ms

style.css

368 ms

xserver.js

920 ms

jquery-1.11.0.min.js

714 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 81% of them (51 requests) were addressed to the original 55w.jp, 13% (8 requests) were made to I0.wp.com and 2% (1 request) were made to Webfonts.xserver.jp. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 564.1 kB (6%)

Content Size

9.4 MB

After Optimization

8.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 55w.jp main page is 9.4 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. 45% of websites need less resources to load. Images take 8.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 59.4 kB

  • Original 74.3 kB
  • After minification 67.4 kB
  • After compression 14.9 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 59.4 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 457.8 kB

  • Original 8.9 MB
  • After minification 8.5 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. 55 W images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 31.9 kB

  • Original 334.2 kB
  • After minification 333.8 kB
  • After compression 302.3 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

-25%

Potential reduce by 15.0 kB

  • Original 60.0 kB
  • After minification 59.0 kB
  • After compression 45.0 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. 55w.jp needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (47%)

Requests Now

62

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.55w.jp

www.55w.jp

1715 ms

normalize.css

normalize.css

184 ms

style.css

style.css

368 ms

xserver.js

xserver.js

920 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

714 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

532 ms

gNavi.js

gNavi.js

539 ms

jQueryRotate.js

jQueryRotate.js

538 ms

jQueryRotateConfig.js

jQueryRotateConfig.js

552 ms

jquery.exflexfixed-0.3.0.js

jquery.exflexfixed-0.3.0.js

556 ms

exflexfixedConfig.js

exflexfixedConfig.js

710 ms

pagetop.js

pagetop.js

718 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

719 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

735 ms

style.min.css

style.min.css

941 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

887 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

888 ms

styles.css

styles.css

897 ms

pagenavi-css.css

pagenavi-css.css

897 ms

jetpack.css

jetpack.css

935 ms

image-cdn.js

image-cdn.js

1064 ms

index.js

index.js

1065 ms

index.js

index.js

1075 ms

api.js

api.js

69 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1077 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1139 ms

wp-polyfill.min.js

wp-polyfill.min.js

1140 ms

index.js

index.js

1240 ms

e-202424.js

e-202424.js

15 ms

jetpack-carousel.min.js

jetpack-carousel.min.js

1241 ms

hatasho.png

hatasho.png

1514 ms

pannellum.htm

pannellum.htm

368 ms

header_logo.png

header_logo.png

315 ms

nav_icn.png

nav_icn.png

315 ms

gnavi_logo.png

gnavi_logo.png

335 ms

side_logo.png

side_logo.png

342 ms

slider_img_05.png

slider_img_05.png

999 ms

slider_img_prgscool.jpg

slider_img_prgscool.jpg

1008 ms

slider_img_human.jpg

slider_img_human.jpg

1200 ms

ggw_sdgs_bnr.jpg

ggw_sdgs_bnr.jpg

1244 ms

slider_img.jpg

slider_img.jpg

1064 ms

slider_img_04.jpg

slider_img_04.jpg

895 ms

banner_img_PCsell.png

banner_img_PCsell.png

1271 ms

arrow_01.png

arrow_01.png

1177 ms

top_bg.jpg

top_bg.jpg

1186 ms

top_img_07.jpg

top_img_07.jpg

1248 ms

top_img_08.jpg

top_img_08.jpg

1355 ms

top_news_no_image.png

top_news_no_image.png

1364 ms

pagetop_btn.png

pagetop_btn.png

1380 ms

icn_12.png

icn_12.png

1424 ms

footer_tel.jpg

footer_tel.jpg

1431 ms

mnheart.png

mnheart.png

1680 ms

6e48ef1b8873c03ed946aba146b605dc.png

6e48ef1b8873c03ed946aba146b605dc.png

1964 ms

158becf7623acb72e516588b660e285d.png

158becf7623acb72e516588b660e285d.png

1756 ms

kyoritu.png

kyoritu.png

1525 ms

648c4e57db373bf73c6feafc3712f346.png

648c4e57db373bf73c6feafc3712f346.png

1877 ms

dc299346d36b7ab923d4a88e426bf0c0.jpeg

dc299346d36b7ab923d4a88e426bf0c0.jpeg

2943 ms

slider_img_prgscool.jpg

slider_img_prgscool.jpg

3080 ms

recaptcha__en.js

recaptcha__en.js

26 ms

picturefill.min.js

picturefill.min.js

1153 ms

matu.json

matu.json

180 ms

room.json

room.json

359 ms

room1.jpg

room1.jpg

2263 ms

Accessibility Review

55w.jp accessibility score

82

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

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

55w.jp best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

55w.jp SEO score

100

Search Engine Optimization Advices

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 55w.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 55w.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

55w.jp

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