Tools & Wizards About Us
guska.jp screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

guska.jp

ベッド専門店グースカ

Page Load Speed

2.9 sec in total

First Response

568 ms

Resources Loaded

2 sec

Page Rendered

329 ms

guska.jp screenshot

About Website

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

「ためして寝」ができるベッドを７０台ほどご用意して、文字通り実際にベッドで「試して」＋「寝てみる」ことができます。いろいろなブランドベッドをひとつのお店（一か所）で「ためして寝」ができるお店は、ベッド専門店の「グースカ」だけ！あなたに最適のベッドを見つけてください。

Visit guska.jp

Key Findings

We analyzed Guska.jp page load time and found that the first response time was 568 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

guska.jp performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value37.9 s

0/100

25%

SI (Speed Index)

Value29.0 s

0/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.428

22/100

15%

TTI (Time to Interactive)

Value37.6 s

0/100

10%

Network Requests Diagram

guska.jp

568 ms

owl.carousel.css

133 ms

owl.theme.css

134 ms

default.css

302 ms

base.css

227 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 95% of them (61 requests) were addressed to the original Guska.jp, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (881 ms) belongs to the original domain Guska.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.4 kB (11%)

Content Size

965.2 kB

After Optimization

859.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 24.0 kB

  • Original 29.6 kB
  • After minification 17.5 kB
  • After compression 5.6 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 12.1 kB, which is 41% 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 24.0 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 16.6 kB

  • Original 807.7 kB
  • After minification 791.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. Guska images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 50.6 kB

  • Original 109.8 kB
  • After minification 84.1 kB
  • After compression 59.2 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 50.6 kB or 46% of the original size.

CSS Optimization

-78%

Potential reduce by 14.2 kB

  • Original 18.1 kB
  • After minification 15.7 kB
  • After compression 3.9 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. Guska.jp needs all CSS files to be minified and compressed as it can save up to 14.2 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

47

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

guska.jp

guska.jp

568 ms

owl.carousel.css

owl.carousel.css

133 ms

owl.theme.css

owl.theme.css

134 ms

default.css

default.css

302 ms

base.css

base.css

227 ms

jquery.min.js

jquery.min.js

7 ms

owl.carousel.js

owl.carousel.js

491 ms

base.js

base.js

194 ms

smoothscroll.js

smoothscroll.js

197 ms

jQueryAutoHeight.js

jQueryAutoHeight.js

258 ms

ga.js

ga.js

74 ms

body_bg.jpg

body_bg.jpg

77 ms

logo.jpg

logo.jpg

78 ms

header_tel.png

header_tel.png

156 ms

header_btn_inq_off.png

header_btn_inq_off.png

131 ms

gnav1_off.png

gnav1_off.png

80 ms

gnav2_off.png

gnav2_off.png

131 ms

gnav3_off.png

gnav3_off.png

152 ms

gnav4_off.png

gnav4_off.png

229 ms

gnav5_off.png

gnav5_off.png

155 ms

gnav6_off.png

gnav6_off.png

259 ms

main1.jpg

main1.jpg

848 ms

main2.jpg

main2.jpg

756 ms

main3.jpg

main3.jpg

643 ms

side_bannar1.jpg

side_bannar1.jpg

380 ms

side_h2_bg.png

side_h2_bg.png

304 ms

arrow_r_orange.png

arrow_r_orange.png

323 ms

side_bannar2.jpg

side_bannar2.jpg

496 ms

contents_h2_bg.png

contents_h2_bg.png

388 ms

p_event3.jpg

p_event3.jpg

455 ms

t_brand1.gif

t_brand1.gif

517 ms

p_brand1.jpg

p_brand1.jpg

531 ms

p_brand2.jpg

p_brand2.jpg

572 ms

p_brand3.jpg

p_brand3.jpg

582 ms

p_brand4.jpg

p_brand4.jpg

607 ms

p_brand5.jpg

p_brand5.jpg

648 ms

p_brand6.jpg

p_brand6.jpg

647 ms

p_brand7.jpg

p_brand7.jpg

683 ms

p_brand8.jpg

p_brand8.jpg

716 ms

p_brand9.jpg

p_brand9.jpg

711 ms

p_brand10.jpg

p_brand10.jpg

723 ms

p_brand11.jpg

p_brand11.jpg

758 ms

btn_brand_off.png

btn_brand_off.png

776 ms

p_floor_3_1.jpg

p_floor_3_1.jpg

792 ms

p_floor_3_2.jpg

p_floor_3_2.jpg

873 ms

p_floor_3_3.jpg

p_floor_3_3.jpg

830 ms

btn_detail_off.png

btn_detail_off.png

832 ms

__utm.gif

__utm.gif

12 ms

p_floor_2_1.jpg

p_floor_2_1.jpg

831 ms

p_floor_2_2.jpg

p_floor_2_2.jpg

792 ms

p_floor_2_3.jpg

p_floor_2_3.jpg

829 ms

p_floor_1_1.jpg

p_floor_1_1.jpg

859 ms

p_floor_1_2.jpg

p_floor_1_2.jpg

783 ms

p_floor_1_3.jpg

p_floor_1_3.jpg

795 ms

p_product8.jpg

p_product8.jpg

799 ms

p_product9.jpg

p_product9.jpg

881 ms

p_product7.jpg

p_product7.jpg

757 ms

p_product4.jpg

p_product4.jpg

721 ms

p_product10.jpg

p_product10.jpg

718 ms

p_product6.jpg

p_product6.jpg

706 ms

news_icon_product.gif

news_icon_product.gif

665 ms

news_icon_media.gif

news_icon_media.gif

673 ms

line_x.png

line_x.png

610 ms

arrow_top.gif

arrow_top.gif

600 ms

Accessibility Review

guska.jp accessibility score

86

Accessibility Issues

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

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

High

Missing source maps for large first-party JavaScript

SEO Factors

guska.jp SEO score

82

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

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

guska.jp

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