7.7 sec in total
1.3 sec
6.3 sec
174 ms
Visit greeeen.co.jp now to see the best up-to-date GReeeeN content for Japan and also check out these interesting facts you probably never knew about greeeen.co.jp
GReeeeN オフィシャルサイト。GReeeeN は HIDE、 navi、 92、 SOHの男性4人組、福島県で結成されたボーカルグループ。
Visit greeeen.co.jpWe analyzed Greeeen.co.jp page load time and found that the first response time was 1.3 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
greeeen.co.jp performance score
name
value
score
weighting
Value4.3 s
19/100
10%
Value14.1 s
0/100
25%
Value12.3 s
3/100
10%
Value700 ms
42/100
30%
Value0.265
46/100
15%
Value16.9 s
5/100
10%
1251 ms
422 ms
424 ms
424 ms
425 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 47% of them (35 requests) were addressed to the original Greeeen.co.jp, 12% (9 requests) were made to Microsofttranslator.com and 8% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Greeeen.co.jp.
Page size can be reduced by 850.2 kB (31%)
2.8 MB
1.9 MB
In fact, the total size of Greeeen.co.jp main page is 2.8 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. 55% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 42.2 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 8.4 kB, which is 16% 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 42.2 kB or 78% of the original size.
Potential reduce by 650.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. Obviously, GReeeeN needs image optimization as it can save up to 650.1 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 117.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 117.3 kB or 36% of the original size.
Potential reduce by 40.6 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. Greeeen.co.jp needs all CSS files to be minified and compressed as it can save up to 40.6 kB or 76% of the original size.
Number of requests can be reduced by 40 (61%)
66
26
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GReeeeN. 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 9 to 1 for CSS and as a result speed up the page load time.
greeeen.co.jp
1251 ms
reset.css
422 ms
layerBoard.css
424 ms
flexslider.css
424 ms
common.css
425 ms
index.css
432 ms
jquery1.7.1-min.js
1348 ms
jquery.cookie.js
789 ms
jquery.layerBoard.js
803 ms
jquery.leanModal.min.js
846 ms
jquery.colorbox.js
1059 ms
jquery.flexslider-min.js
1084 ms
index.js
1168 ms
style.min.css
1397 ms
styles.css
1280 ms
js
64 ms
bookmark_button.js
12 ms
platform.js
20 ms
wp-embed.min.js
1333 ms
bookmark_button.js
14 ms
developers.line.biz
536 ms
developers.line.biz
702 ms
wp-emoji-release.min.js
199 ms
button-only@2x.png
16 ms
addfriends_ja.png
353 ms
common_bg.jpg
2817 ms
common_logo_w.png
632 ms
common_logo_sp.png
849 ms
menu_sp.png
441 ms
modal_logo.png
632 ms
modal_close.png
613 ms
GRN_760x380-2.jpg
2748 ms
GRN_web_header1_760380.png
3188 ms
GRN_760x380-1.jpg
2514 ms
GRN_760x380-1.jpg
2330 ms
FC.jpg
2591 ms
logo_greeeen02.jpg
3063 ms
d5600f60ea4951c601a82a52df1ffab4.jpg
3645 ms
jda-2.jpg
3246 ms
button-only@2x.png
6 ms
sdk.js
30 ms
common_menu_bg.png
3108 ms
WidgetV3.ashx
111 ms
common_bg_post.png
3168 ms
widgets.js
15 ms
sdk.js
14 ms
cb=gapi.loaded_0
9 ms
cb=gapi.loaded_1
62 ms
fastbutton
59 ms
postmessageRelay
27 ms
3636781319-postmessagerelay.js
15 ms
rpc:shindig_random.js
6 ms
cb=gapi.loaded_0
7 ms
developers.google.com
791 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
42 ms
flexslider-icon.woff
3179 ms
like.php
232 ms
settings
101 ms
addfriends_ja.png
695 ms
button.856debeac157d9669cf51e73a08fbc93.js
2 ms
embeds
27 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html
15 ms
7Sq0vGHTbTI.js
37 ms
FEppCFCt76d.png
29 ms
to-top_bg.png
219 ms
close_x.png
7 ms
WidgetV3.css
14 ms
metrics.js
32 ms
WidgetLauncher.css
16 ms
bingmark.png
12 ms
fbookmark.png
12 ms
email_icon.png
13 ms
embed_question.png
13 ms
binglogo_dark.png
27 ms
greeeen.co.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
greeeen.co.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
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
greeeen.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greeeen.co.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 Greeeen.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.
greeeen.co.jp
Open Graph data is detected on the main page of GReeeeN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: