11.3 sec in total
717 ms
9.8 sec
722 ms
Click here to check amazing Five G content for Japan. Otherwise, check out these important facts you probably never knew about fiveg.net
シンセサイザー、ヴィンテージシンセ、アナログシンセ、ユーロラック・モジュラーシンセの販売と買取を行う楽器店 Five G music technology のオンライン通販ページです。東京 原宿の店舗でも取扱商品を多数展示、販売しています。
Visit fiveg.netWe analyzed Fiveg.net page load time and found that the first response time was 717 ms and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fiveg.net performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value7.6 s
4/100
25%
Value6.5 s
38/100
10%
Value510 ms
57/100
30%
Value0.765
5/100
15%
Value8.0 s
42/100
10%
717 ms
325 ms
270 ms
707 ms
29 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 9% of them (11 requests) were addressed to the original Fiveg.net, 72% (90 requests) were made to Img20.shop-pro.jp and 6% (7 requests) were made to File001.shop-pro.jp. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Img20.shop-pro.jp.
Page size can be reduced by 479.4 kB (13%)
3.8 MB
3.3 MB
In fact, the total size of Fiveg.net main page is 3.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 3.5 MB which makes up the majority of the site volume.
Potential reduce by 61.9 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 12.1 kB, which is 17% 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 61.9 kB or 86% of the original size.
Potential reduce by 283.5 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. Five G images are well optimized though.
Potential reduce by 96.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 96.9 kB or 56% of the original size.
Potential reduce by 37.0 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. Fiveg.net needs all CSS files to be minified and compressed as it can save up to 37.0 kB or 83% of the original size.
Number of requests can be reduced by 27 (22%)
124
97
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Five G. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
fiveg.net
717 ms
cross-border-cart.css
325 ms
index.css
270 ms
top.css
707 ms
jquery.min.js
29 ms
lightbox.css
548 ms
jquery-1-11-0-min.js
960 ms
lightbox.js
580 ms
jquery.bxslider.css
319 ms
jquery.bxslider.min.js
322 ms
cart.js
341 ms
product_stock.js
364 ms
li.php
501 ms
li.php
592 ms
header_fiveg.jpg
302 ms
left-navi_bg.gif
224 ms
icons7.gif
324 ms
logo_fiveg.png
288 ms
header_fiveg_text.png
288 ms
kyujin.jpg
472 ms
bannar_fiveg_insta.jpg
406 ms
bannar_yahoo_auction.jpg
577 ms
bannar_kaitori_top.jpg
900 ms
bannar_welcome.jpg
579 ms
bannar_museum.jpg
703 ms
bannar_fiveg_faq.jpg
676 ms
bannar_vintage_faq.jpg
756 ms
slideshow_img0.jpg
1066 ms
slideshow_img1.jpg
1731 ms
slideshow_img2.jpg
1687 ms
slideshow_img3.jpg
1454 ms
bannar_kaitori_vintage1501.jpg
1177 ms
bannar_kaitori_used1501.jpg
1342 ms
bannar_mellotron_02.jpg
1613 ms
bannar_boomstar.jpg
1599 ms
bannar_mutable_braids.jpg
2061 ms
bannar_rt451.jpg
2076 ms
bannar_prophet6module.jpg
2128 ms
bannar_prophet6_2.jpg
1993 ms
bannar_modstar_min.jpg
2159 ms
bannar_minilogue.jpg
2222 ms
bannar_jd_xaxi.jpg
2474 ms
bannar_doepfer_wasp.jpg
2681 ms
808_bdwav_RBMA.jpg
2568 ms
99446921_th.jpg
2574 ms
99446766_th.jpg
2609 ms
99446297_th.jpg
2868 ms
99446194_th.jpg
2958 ms
99142573_th.jpg
3037 ms
99141900_th.jpg
3340 ms
99141791_th.jpg
3237 ms
99141745_th.jpg
3158 ms
close.png
239 ms
loading.gif
280 ms
prev.png
236 ms
next.png
674 ms
rs_m_rect.gif
201 ms
left-navi_bg03.gif
202 ms
rs_m_cart_btn.gif
207 ms
rss.gif
201 ms
atom.gif
206 ms
icons5.gif
338 ms
icons29.gif
342 ms
icons41.gif
366 ms
widgets.js
84 ms
bx_loader.gif
357 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
129 ms
syndication
91 ms
545439814061805568
155 ms
99141611_th.jpg
3070 ms
99141550_th.jpg
3383 ms
99141512_th.jpg
3223 ms
91040560_th.jpg
3023 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
30 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
128 ms
99400756_th.jpg
3209 ms
wCiGQyMw_normal.jpeg
94 ms
91040602_th.jpg
3285 ms
99401356_th.jpg
3447 ms
98278807_th.jpg
3336 ms
96827344_th.jpg
3296 ms
97894549_th.jpg
3361 ms
jot
26 ms
97894655_th.jpg
3259 ms
97536405_th.jpg
3427 ms
96947098_th.jpg
3487 ms
89778759_th.jpg
3219 ms
89780352_th.jpg
3034 ms
96825444_th.jpg
2931 ms
96827310_th.jpg
3003 ms
89780302_th.jpg
3220 ms
89778849_th.jpg
3252 ms
96825862_th.jpg
2796 ms
89780077_th.jpg
3145 ms
96826547_th.jpg
3142 ms
96827184_th.jpg
3019 ms
96662190_th.jpg
3075 ms
96254656_th.jpg
3173 ms
96254685_th.jpg
2951 ms
96254722_th.jpg
3045 ms
96254781_th.jpg
3321 ms
96254839_th.jpg
3229 ms
96254901_th.jpg
3100 ms
93330294_th.jpg
3400 ms
93330395_th.jpg
3357 ms
93330521_th.jpg
3024 ms
93330603_th.jpg
3079 ms
91039994_th.jpg
3535 ms
91039957_th.jpg
2979 ms
91040049_th.jpg
3136 ms
91040027_th.jpg
3360 ms
93953709_th.jpg
3334 ms
90971400_th.jpg
3397 ms
82194621_th.jpg
3535 ms
82194624_th.jpg
3051 ms
81462962_th.jpg
3302 ms
81462965_th.jpg
3265 ms
90900779_th.jpg
3418 ms
82278357_th.jpg
3105 ms
86200681_th.jpg
3378 ms
82215275_th.jpg
3344 ms
82215277_th.jpg
3507 ms
82189135_th.jpg
3263 ms
82189138_th.jpg
3534 ms
logo_fiveg_footer.png
3235 ms
fiveg.net 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
Image elements do not have [alt] attributes
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.
fiveg.net 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
Browser errors were logged to the console
fiveg.net 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
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fiveg.net 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 Fiveg.net main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
fiveg.net
Open Graph data is detected on the main page of Five G. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: