Access gomihikaku.com. 不用品回収・粗大ごみ比較ナビ - 不用品・粗大ごみ回収業者の特徴や料金、口コミを比較

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

gomihikaku.com

530 ms

gomihikaku.com

977 ms

import.css

180 ms

inc.css

360 ms

swfobject.js

545 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 87% of them (93 requests) were addressed to the original Gomihikaku.com, 3% (3 requests) were made to Ssl.google-analytics.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Api.omni-databank.com.

Content Size

891.2 kB

After Optimization

844.4 kB

In fact, the total size of Gomihikaku.com main page is 891.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. 55% of websites need less resources to load. Images take 726.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 32.8 kB

Original 42.5 kB
After minification 40.3 kB
After compression 9.7 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 32.8 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 4.3 kB

Original 726.4 kB
After minification 722.0 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. Gomihikaku images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.2 kB

Original 103.9 kB
After minification 103.9 kB
After compression 102.7 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

-46%

Potential reduce by 8.4 kB

Original 18.5 kB
After minification 15.2 kB
After compression 10.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. Gomihikaku.com needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 46% of the original size.

Requests Now

102

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

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

gomihikaku.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

不用品回収・粗大ごみ比較ナビ - 不用品・粗大ごみ回収業者の特徴や料金、口コミを比較

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

gomihikaku.com

gomihikaku.com

import.css

inc.css

swfobject.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

gomihikaku.com

gomihikaku.com

import.css

inc.css

swfobject.js

kw.js

kw2.js

prototype.js

addrajax.js

addrajax.js

ua_check.js

conversion.js

s_retargeting.js

default.css

base.css

contents.css

common.css

area.css

city.css

ga.js

gtm.js

bg.gif

head_bg.jpg

head_btn01.jpg

head_btn04.jpg

logo.jpg

head_catch.gif

c_btn_01.jpg

c_btn_02.jpg

c_btn_03.jpg

top_flabox.gif

top_left_bg.png

company_all.gif

menu01_f.jpg

menu02.jpg

menu03.jpg

menu04.jpg

menu05.jpg

menu07.jpg

menu06.jpg

timthumb.php

timthumb.php

side-column-btn.png