6.9 sec in total
1.8 sec
5 sec
224 ms
Click here to check amazing Greensheep content. Otherwise, check out these important facts you probably never knew about greensheep.co.jp
お客様の抱えるWebビジネスの改善提案と最適なシステム設計、運用保守に至るまで、低コストで支援いたします。
Visit greensheep.co.jpWe analyzed Greensheep.co.jp page load time and found that the first response time was 1.8 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
greensheep.co.jp performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value11.8 s
0/100
25%
Value22.2 s
0/100
10%
Value260 ms
83/100
30%
Value0.145
77/100
15%
Value12.3 s
15/100
10%
1767 ms
369 ms
359 ms
1044 ms
379 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 96% of them (50 requests) were addressed to the original Greensheep.co.jp, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Greensheep.co.jp.
Page size can be reduced by 143.1 kB (43%)
336.3 kB
193.2 kB
In fact, the total size of Greensheep.co.jp main page is 336.3 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. 15% of websites need less resources to load. Javascripts take 163.8 kB which makes up the majority of the site volume.
Potential reduce by 15.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. 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 15.6 kB or 77% of the original size.
Potential reduce by 245 B
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. Greensheep images are well optimized though.
Potential reduce by 108.9 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 108.9 kB or 66% of the original size.
Potential reduce by 18.3 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. Greensheep.co.jp needs all CSS files to be minified and compressed as it can save up to 18.3 kB or 81% of the original size.
Number of requests can be reduced by 31 (61%)
51
20
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greensheep. 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 6 to 1 for CSS and as a result speed up the page load time.
www.greensheep.co.jp
1767 ms
style.css
369 ms
1st.css
359 ms
jquery-1.4.2.min.js
1044 ms
scroll.js
379 ms
rollover.js
383 ms
dammy.css
180 ms
common.css
186 ms
layout.css
206 ms
wp-embed.min.js
207 ms
wp-emoji-release.min.js
217 ms
analytics.js
57 ms
bgBody.gif
192 ms
001.jpg
706 ms
bgHead.jpg
198 ms
index_H1.gif
197 ms
mainImg2.jpg
182 ms
bg_headRight.gif
372 ms
h204.gif
382 ms
bg_gNaviBox.gif
383 ms
gNavi01_on.gif
385 ms
gNavi02.gif
407 ms
bg_contBox.gif
550 ms
rss01.gif
573 ms
contBn01_ov.gif
568 ms
contBn01.gif
571 ms
arw04.gif
602 ms
bgDotted01.gif
729 ms
01.jpg
746 ms
arw01.gif
758 ms
02.jpg
763 ms
bg_subNaviBox.gif
796 ms
subNavi01_on.gif
879 ms
subNavi02.gif
907 ms
bg_subBox.gif
921 ms
bgDotted02.gif
947 ms
03.jpg
952 ms
04.jpg
989 ms
06.jpg
1063 ms
07.jpg
1085 ms
05.jpg
1097 ms
08.jpg
1135 ms
bg_footPTop.gif
1140 ms
footPtop01.gif
1183 ms
footPtop02.gif
1239 ms
bg_footBox.gif
1265 ms
fNavi01_on.gif
1235 ms
collect
10 ms
fNavi02.gif
1148 ms
bg_fLogo.gif
1149 ms
bg_address.gif
1189 ms
print.css
197 ms
greensheep.co.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
greensheep.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
greensheep.co.jp SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greensheep.co.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 Greensheep.co.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.
greensheep.co.jp
Open Graph description is not detected on the main page of Greensheep. 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: