8.4 sec in total
660 ms
7.2 sec
476 ms
Click here to check amazing Grinpia content. Otherwise, check out these important facts you probably never knew about grinpia.com
広がる大茶園で、お茶体験からショッピングまでお茶を楽しむグリンピア牧之原。 お茶の卸問屋である株式会社喜作園の運営する施設です。本場お茶処の商品をご購入なら ネット通販サイト「グリンピア牧之原ネットショップ」へぜひどうぞ!!
Visit grinpia.comWe analyzed Grinpia.com page load time and found that the first response time was 660 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
grinpia.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value15.5 s
0/100
25%
Value8.0 s
22/100
10%
Value1,280 ms
18/100
30%
Value0.217
57/100
15%
Value18.0 s
3/100
10%
660 ms
347 ms
354 ms
360 ms
371 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 84% of them (70 requests) were addressed to the original Grinpia.com, 4% (3 requests) were made to Static.tacdn.com and 4% (3 requests) were made to Tripadvisor.jp. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Grinpia.com.
Page size can be reduced by 172.8 kB (11%)
1.6 MB
1.5 MB
In fact, the total size of Grinpia.com main page is 1.6 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 21.3 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 21.3 kB or 76% of the original size.
Potential reduce by 92.9 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. Grinpia images are well optimized though.
Potential reduce by 44.5 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 44.5 kB or 62% of the original size.
Potential reduce by 14.1 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. Grinpia.com needs all CSS files to be minified and compressed as it can save up to 14.1 kB or 79% of the original size.
Number of requests can be reduced by 23 (28%)
81
58
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grinpia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
grinpia.com
660 ms
import.css
347 ms
common.js
354 ms
showmenu.js
360 ms
convert.js
371 ms
wejs
104 ms
default.css
196 ms
layout.css
335 ms
style.css
361 ms
iepngfix.js
175 ms
heightLine.js
185 ms
rollover.js
338 ms
Stacked_TA_logo.png
153 ms
589867597711052.3054.280231935.png
283 ms
tripadvisor_sticker_logo_88x55-18961-2.png
60 ms
hed_logo.jpg
673 ms
btn_tub01.gif
349 ms
btn_tub02.gif
356 ms
img_cnt_tel.gif
367 ms
img_cnt_tim.gif
372 ms
btn_head_exp.jpg
378 ms
btn_head_vis.jpg
680 ms
btn_head_meal.jpg
688 ms
btn_head_shop.jpg
709 ms
bg_main_top.jpg
1314 ms
mimg-p1.jpg
3663 ms
45.jpg
1393 ms
1.gif
1025 ms
83.jpg
1384 ms
47.jpg
1411 ms
48.jpg
1690 ms
256.jpg
1846 ms
51.jpg
1717 ms
230.jpg
2059 ms
255.jpg
2149 ms
214.jpg
2199 ms
215.jpg
2231 ms
183.jpg
4187 ms
159.jpg
3117 ms
75.jpg
2734 ms
76.jpg
2699 ms
34.jpg
2758 ms
147.jpg
3246 ms
27.jpg
4045 ms
ttl_side_shop.png
3344 ms
btn_side_shop.gif
3518 ms
btn_side_member.gif
3638 ms
ttl_side_menu.gif
3682 ms
btn_side_cont.jpg
3888 ms
ttl_side_info.gif
3987 ms
pv_beacon.gif
346 ms
brn_site_other.gif
4022 ms
WidgetEmbed-cdsscrollingravewide
70 ms
cdswidget-scrollingrave-v2823050010a.css%20%27%29%3B
4 ms
cdswidgets_min-c-v23892882724a.js
72 ms
cdswidget-scrollingrave-v2823050010a.css
87 ms
analytics.js
80 ms
collect
13 ms
btn_kisakuen.jpg
3679 ms
btn_gurinpia.jpg
3905 ms
btn_gurinpianet.jpg
3997 ms
ttl_h3.gif
4003 ms
bg_side_menufot.gif
4008 ms
51.jpg
335 ms
bg_side_menu.gif
3769 ms
icn_menu_n.gif
3859 ms
bg_side_infofot.gif
3922 ms
bg_side_info.gif
4027 ms
bg_foot.jpg
4056 ms
btn_pagetop.jpg
3431 ms
bg_footer.jpg
3429 ms
bg_footer_b.jpg
3496 ms
ftr_img.jpg
3744 ms
bg_foot_g.jpg
3389 ms
foot_bg2.jpg
3357 ms
transparent_pixel-17198-2.gif
14 ms
btn_tub01_o.gif
180 ms
btn_tub02_o.gif
334 ms
btn_head_exp_o.jpg
335 ms
btn_head_vis_o.jpg
346 ms
btn_head_meal_o.jpg
362 ms
btn_head_shop_o.jpg
391 ms
btn_side_cont_o.jpg
535 ms
grinpia.com 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
grinpia.com 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
grinpia.com 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
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 Grinpia.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 Grinpia.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.
grinpia.com
Open Graph description is not detected on the main page of Grinpia. 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: