7.2 sec in total
662 ms
6.4 sec
175 ms
Welcome to grapecom.jp homepage info - get ready to check GRAPE Com best content for Japan right away, or after learning these important things about grapecom.jp
芸能プロダクション、株式会社グレープカンパニーの公式サイト。サンドウィッチマン・永野・カミナリ・高橋英樹・高橋真麻などが所属。ライブ情報、チケット情報、グッズ情報、スケジュールなどを紹介。
Visit grapecom.jpWe analyzed Grapecom.jp page load time and found that the first response time was 662 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
grapecom.jp performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value28.6 s
0/100
25%
Value15.7 s
0/100
10%
Value3,810 ms
1/100
30%
Value0.444
21/100
15%
Value31.1 s
0/100
10%
662 ms
41 ms
577 ms
380 ms
385 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 95% of them (56 requests) were addressed to the original Grapecom.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 (4 sec) belongs to the original domain Grapecom.jp.
Page size can be reduced by 74.9 kB (11%)
678.6 kB
603.7 kB
In fact, the total size of Grapecom.jp main page is 678.6 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. 20% of websites need less resources to load. Images take 570.0 kB which makes up the majority of the site volume.
Potential reduce by 9.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. 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 9.2 kB or 72% of the original size.
Potential reduce by 1.2 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. GRAPE Com images are well optimized though.
Potential reduce by 36.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 36.9 kB or 59% of the original size.
Potential reduce by 27.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. Grapecom.jp needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 83% of the original size.
Number of requests can be reduced by 16 (28%)
58
42
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GRAPE Com. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
grapecom.jp
662 ms
jquery.js
41 ms
myplugin.js
577 ms
overlay.js
380 ms
common.js
385 ms
import.css
382 ms
ga.js
52 ms
basic.css
366 ms
common.css
374 ms
structure.css
381 ms
parts.css
385 ms
common.css
390 ms
page.css
392 ms
hdr_nav_01.gif
707 ms
hdr_nav_02.gif
709 ms
hdr_nav_03.gif
706 ms
title_check.gif
725 ms
title_pickup.gif
922 ms
PRDVD2015.jpg
1897 ms
title_news.gif
1078 ms
btn_more.gif
1077 ms
title_goods.gif
1087 ms
amazon.jpg
1666 ms
719oLGCBODL.jpg
1491 ms
______DVD___140.jpg
1966 ms
______111x45.jpg
1641 ms
__top.jpg
1647 ms
__________.jpg
2071 ms
fujitablog.jpg
2203 ms
twitter.jpg
2191 ms
gree.jpg
2248 ms
______111x45.jpg
2253 ms
geinin.jpg
2525 ms
icon_rss.gif
2425 ms
ftr_company.gif
2541 ms
ftr_mail.png
2574 ms
ftr_tel.png
2604 ms
ftr_fax.png
2619 ms
copyright.gif
2811 ms
siteby.gif
2877 ms
site_title.gif
3099 ms
gNav_01.gif
2931 ms
gNav_02.gif
2954 ms
__utm.gif
24 ms
gNav_03.gif
2683 ms
gNav_04.gif
2848 ms
gNav_05.gif
2900 ms
gNav_06.gif
2954 ms
gNav_01_o.gif
3001 ms
gNav_02_o.gif
3036 ms
gNav_03_o.gif
2779 ms
gNav_04_o.gif
2835 ms
gNav_05_o.gif
2880 ms
gNav_06_o.gif
2960 ms
loading.gif
2805 ms
bg_body.gif
2700 ms
bg_inner_body.jpg
4012 ms
line_01.gif
2813 ms
bg_footer.gif
3039 ms
grapecom.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-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
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.
grapecom.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
Page has valid source maps
grapecom.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 Grapecom.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 Grapecom.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.
grapecom.jp
Open Graph description is not detected on the main page of GRAPE Com. 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: