8.4 sec in total
904 ms
7.1 sec
418 ms
Visit razor.co.jp now to see the best up-to-date Razor content for Japan and also check out these interesting facts you probably never knew about razor.co.jp
キックボード、部品販売のJDRAZORオフィシャルサイト。世界のスタンダードキックスクーター、スケートボード、トレーニングバイク、ホッピングをはじめ様々なアイテムをご紹介。
Visit razor.co.jpWe analyzed Razor.co.jp page load time and found that the first response time was 904 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
razor.co.jp performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value18.8 s
0/100
25%
Value11.4 s
5/100
10%
Value3,610 ms
1/100
30%
Value0
100/100
15%
Value17.8 s
4/100
10%
904 ms
1929 ms
414 ms
416 ms
442 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 94% of them (66 requests) were addressed to the original Razor.co.jp, 4% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Adobe.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Razor.co.jp.
Page size can be reduced by 220.3 kB (14%)
1.5 MB
1.3 MB
In fact, the total size of Razor.co.jp main page is 1.5 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. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 62.7 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 62.7 kB or 80% of the original size.
Potential reduce by 32.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. Razor images are well optimized though.
Potential reduce by 106.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 106.3 kB or 62% of the original size.
Potential reduce by 19.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. Razor.co.jp needs all CSS files to be minified and compressed as it can save up to 19.0 kB or 82% of the original size.
Number of requests can be reduced by 9 (13%)
68
59
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Razor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
razor.co.jp
904 ms
www.razor.co.jp
1929 ms
version4.css
414 ms
import.css
416 ms
lightbox.css
442 ms
scriptaculous.js
460 ms
swfobject_modified.js
847 ms
jquery-1.7.2.min.js
1488 ms
jquery-ui-1.8.18.custom.min.js
1048 ms
jquery.smooth-scroll.min.js
676 ms
lightbox.js
886 ms
base.css
891 ms
ga.js
151 ms
get_flash_player.gif
147 ms
bg_header.jpg
813 ms
logo.jpg
942 ms
bg_navi.jpg
566 ms
navi01.jpg
365 ms
navi02.jpg
309 ms
navi03.jpg
375 ms
navi04.jpg
576 ms
navi05.jpg
601 ms
navi06.jpg
637 ms
navi_cart.jpg
843 ms
navi_contact.jpg
869 ms
bg_info.jpg
873 ms
top_info.jpg
1082 ms
side_category.jpg
1103 ms
icon_link.gif
1114 ms
side_search.gif
1158 ms
btn_search.jpg
1131 ms
side_help.jpg
1185 ms
icon_link2.gif
1341 ms
side_shop.jpg
1376 ms
side_shop_01.gif
1372 ms
side_shop_02.gif
1368 ms
top_campaign.jpg
1602 ms
top_ms500.jpg
2438 ms
top_citybug.jpg
2388 ms
top_banner27.jpg
2104 ms
top_banner28.jpg
2173 ms
top_banner03.jpg
1761 ms
top_banner06.jpg
1922 ms
top_banner29.jpg
2016 ms
top_banner08.jpg
2324 ms
top_banner04.jpg
2280 ms
top_banner30.jpg
2503 ms
top_banner26.jpg
2600 ms
top_banner21.jpg
2535 ms
top_banner31.jpg
2648 ms
__utm.gif
25 ms
__utm.gif
15 ms
top_banner13.jpg
2336 ms
top_banner23.jpg
2353 ms
top_banner11.jpg
2554 ms
top_banner12.jpg
2285 ms
top_banner12_2.jpg
2319 ms
top_banner24.jpg
2309 ms
top_banner15.jpg
2313 ms
top_banner15_2.jpg
2161 ms
top_banner10.jpg
2299 ms
top_banner16.jpg
2918 ms
top_banner17.jpg
2341 ms
top_banner18.jpg
2441 ms
top_banner19.jpg
2139 ms
bg_pagetop.jpg
2110 ms
pagetop.gif
2279 ms
copy.gif
2295 ms
loading.gif
2304 ms
close.png
2272 ms
razor.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
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
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
razor.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
razor.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Razor.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 Razor.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.
razor.co.jp
Open Graph description is not detected on the main page of Razor. 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: