5.1 sec in total
611 ms
4.3 sec
163 ms
Welcome to g-speed.jp homepage info - get ready to check G Speed best content for Japan right away, or after learning these important things about g-speed.jp
Audiを専門にドイツ本国純正パーツ、純正アクセサリー、純正OEM parts、社外パーツ、エンブレム、キーリング等をショッピングカート方式で通信販売しております。オンラインで注文と支払いが完了しましたらあとはご自宅で商品が宅配されるのを待つだけと簡単です。また掲載されていない商品でも国内や海外からのお取り寄せが可能ですのでお手数ですがお問い合わせください。お支払い方法は銀行振込、代金引換発送、電...
Visit g-speed.jpWe analyzed G-speed.jp page load time and found that the first response time was 611 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
g-speed.jp performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value3.9 s
52/100
25%
Value6.4 s
40/100
10%
Value90 ms
98/100
30%
Value0.028
100/100
15%
Value3.9 s
88/100
10%
611 ms
193 ms
348 ms
347 ms
364 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 92% of them (60 requests) were addressed to the original G-speed.jp, 3% (2 requests) were made to Yamatofinancial.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Yamatofinancial.jp.
Page size can be reduced by 560.1 kB (69%)
809.9 kB
249.8 kB
In fact, the total size of G-speed.jp main page is 809.9 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. 30% of websites need less resources to load. Javascripts take 548.0 kB which makes up the majority of the site volume.
Potential reduce by 50.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. This page needs HTML code to be minified as it can gain 18.5 kB, which is 31% 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 50.6 kB or 86% of the original size.
Potential reduce by 20.4 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, G Speed needs image optimization as it can save up to 20.4 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 416.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 416.3 kB or 76% of the original size.
Potential reduce by 72.8 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. G-speed.jp needs all CSS files to be minified and compressed as it can save up to 72.8 kB or 88% of the original size.
Number of requests can be reduced by 22 (35%)
62
40
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G Speed. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
www.g-speed.jp
611 ms
ocnk.js
193 ms
common.css
348 ms
column2.css
347 ms
20091023101328943fa3.css
364 ms
jquery.js
594 ms
underscore.js
367 ms
prototype.js
783 ms
flipsnap.js
518 ms
jquerypp.custom.js
518 ms
jquery.swipeList-min.js
545 ms
jquery.collapser-min.js
548 ms
shared-tool-min.js
692 ms
common.js
689 ms
form-check.js
727 ms
PayPal_mark_60x38.gif
101 ms
web_col_logo.gif
1604 ms
bg.gif
193 ms
20160106_f74b47.jpg
544 ms
copy_bg.gif
185 ms
icon01.gif
185 ms
bot_bg.gif
175 ms
menu_bg02.gif
175 ms
menu_bg01.gif
345 ms
menu_bg_sh.gif
345 ms
icon04.gif
366 ms
menu_bg03.gif
367 ms
cart.gif
383 ms
icon03.gif
515 ms
ssl.gif
517 ms
top_title_bg01.gif
547 ms
text_bg.gif
549 ms
70726f647563742f32303136303232395f3965376164342e4a50470038300000660066.jpg
574 ms
70726f647563742f32303136303232395f3762356234632e4a50470038300000660066.jpg
685 ms
70726f647563742f32303134303631385f6637633563632e6a70670038300000660066.jpg
686 ms
70726f647563742f643464633035343762372e4a50470038300000660066.jpg
723 ms
70726f647563742f746f677377352e4a50470038300000660066.jpg
729 ms
70726f647563742f32303136303231365f3365356130622e4a50470038300000660066.jpg
730 ms
70726f647563742f32303136303231365f3264343432382e6a70670038300000660066.jpg
766 ms
70726f647563742f32303136303131315f3734386435632e4a50470038300000660066.jpg
856 ms
70726f647563742f32303135313232335f6463393430332e4a50470038300000660066.jpg
859 ms
70726f647563742f32303135313232345f3835636561622e4a50470038300000660066.jpg
902 ms
70726f647563742f32303135303631395f3965643630302e4a50470038300000660066.jpg
910 ms
70726f647563742f32303135303232335f3438393636322e4a50470038300000660066.jpg
911 ms
70726f647563742f32303133303630335f3436613662352e6a70670038300000660066.jpg
956 ms
70726f647563742f32303135303331385f3664376430362e4a50470038300000660066.jpg
1027 ms
70726f647563742f32303132303630325f3633663634322e6a70670038300000660066.jpg
1029 ms
70726f647563742f32303134303133305f3930613539332e6a70670038300000660066.jpg
1082 ms
menu_bg04.gif
1092 ms
70726f647563742f32303132303931385f3862363461352e4a50470038300000660066.jpg
1093 ms
70726f647563742f32303132303932385f3333343031632e6a70670038300000660066.jpg
1147 ms
70726f647563742f32303135313130355f6437636561632e4a50470038300000660066.jpg
1197 ms
70726f647563742f32303135313032375f3963326435362e4a50470038300000660066.jpg
1172 ms
ga.js
23 ms
__utm.gif
21 ms
xml.php
1105 ms
70726f647563742f393762386365646131302e6a70670038300000660066.jpg
1102 ms
70726f647563742f32303135303330335f3566326266312e4a50470038300000660066.jpg
1095 ms
70726f647563742f32303135313132315f6237366565382e6a70670038300000660066.jpg
1158 ms
70726f647563742f346232663563343230372e4a50470038300000660066.jpg
1181 ms
counter.php
1046 ms
rss10.gif
1116 ms
load.gif
1096 ms
clear.gif
182 ms
web_col_logo.gif
670 ms
g-speed.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 valid value for its [lang] attribute.
g-speed.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
g-speed.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 G-speed.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 G-speed.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.
g-speed.jp
Open Graph description is not detected on the main page of G Speed. 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: