1.6 sec in total
759 ms
770 ms
114 ms
Welcome to greenpillow.jp homepage info - get ready to check Greenpillow best content right away, or after learning these important things about greenpillow.jp
ぐおぉぉぉぉぉぉぉぉ!という破壊的ないびきを日常的にしているなら、一度セルフチェックをしてみてはどうでしょう?!睡眠時無呼吸症候群(SAS)かも知れませんよ。日中の突然襲ってくる睡魔だったり、実際に一瞬の睡魔で甚大な事故になる可能性もあります。睡眠時無呼吸症候群SASかどうかを検査するのに、健康保険も適用されて治療にも保険適用になります。中高年だけではなく、子供のいびきにも注意が必要です。
Visit greenpillow.jpWe analyzed Greenpillow.jp page load time and found that the first response time was 759 ms and then it took 884 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
greenpillow.jp performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value4.1 s
47/100
25%
Value3.3 s
90/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value4.1 s
87/100
10%
759 ms
Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Greenpillow.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (759 ms) belongs to the original domain Greenpillow.jp.
Page size can be reduced by 88 B (28%)
320 B
232 B
In fact, the total size of Greenpillow.jp main page is 320 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 320 B which makes up the majority of the site volume.
Potential reduce by 88 B
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 88 B or 28% of the original size.
We found no issues to fix!
0
0
Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.
greenpillow.jp
759 ms
greenpillow.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
greenpillow.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
greenpillow.jp SEO score
JA
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenpillow.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Greenpillow.jp main page’s claimed encoding is iso-8859-1. 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.
greenpillow.jp
Open Graph description is not detected on the main page of Greenpillow. 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: