8 sec in total
623 ms
6.7 sec
690 ms
Click here to check amazing HEXADRIVE content for Japan. Otherwise, check out these important facts you probably never knew about hexadrive.jp
ヘキサドライブは、ゲーム制作を中心としたコンテンツクリエイト会社です。HEXA(ヘキサ)はギリシア語で「6」を意味する言葉です。人間の持つ5感に心を加えた6感を躍動(DRIVE)させるようなコンテンツを作るという意味を込めて名付けました。ヘキサドライブは、社員の幸せを追求し、そしてより良いコンテンツを作ることに挑戦し続けます。
Visit hexadrive.jpWe analyzed Hexadrive.jp page load time and found that the first response time was 623 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hexadrive.jp performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value6.5 s
9/100
25%
Value13.8 s
1/100
10%
Value220 ms
87/100
30%
Value0.269
45/100
15%
Value10.2 s
25/100
10%
623 ms
1217 ms
335 ms
649 ms
984 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 83% of them (53 requests) were addressed to the original Hexadrive.jp, 6% (4 requests) were made to Fonts.googleapis.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Hexadrive.jp.
Page size can be reduced by 469.5 kB (5%)
8.8 MB
8.3 MB
In fact, the total size of Hexadrive.jp main page is 8.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. 60% of websites need less resources to load. Images take 8.3 MB which makes up the majority of the site volume.
Potential reduce by 34.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 34.7 kB or 79% of the original size.
Potential reduce by 98.1 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. HEXADRIVE images are well optimized though.
Potential reduce by 234.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 234.3 kB or 68% of the original size.
Potential reduce by 102.5 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. Hexadrive.jp needs all CSS files to be minified and compressed as it can save up to 102.5 kB or 84% of the original size.
Number of requests can be reduced by 31 (53%)
59
28
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HEXADRIVE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
hexadrive.jp
623 ms
hexadrive.jp
1217 ms
format.css
335 ms
base.css
649 ms
page.css
984 ms
index.css
496 ms
font.css
527 ms
animation.css
601 ms
icon.css
609 ms
magnific-popup.css
658 ms
jquery.bxslider.css
703 ms
slick.css
801 ms
styles.css
812 ms
default.css
809 ms
jquery.min.js
21 ms
external-tracking.min.js
819 ms
function.js
878 ms
jquery.taphover.js
1035 ms
jquery.crossFader.js
971 ms
jquery.magnific-popup.min.js
1216 ms
jquery.mixitup.min.js
980 ms
jquery.customSelect.js
1060 ms
jquery.bxslider.js
1455 ms
slick.min.js
1142 ms
scripts.js
976 ms
prettify.js
1619 ms
load.js
1060 ms
wp-embed.min.js
1136 ms
css
33 ms
css
50 ms
css
56 ms
css
60 ms
wp-emoji-release.min.js
292 ms
analytics.js
16 ms
collect
13 ms
js
73 ms
slide-anni15.jpg
343 ms
slide-anni15-s.jpg
410 ms
slide-voidcrisis.jpg
2280 ms
slide-voidcrisis-s.jpg
1423 ms
slide02.jpg
1615 ms
slide02-s.jpg
1327 ms
slide03.jpg
1944 ms
slide03-s.jpg
1578 ms
4a4bad6f327b890a37bab30a584f85a3.jpg
1727 ms
e2e280ccf5e68776c9becc9d41b963bd.jpg
1829 ms
d9219663497c2854383fea1465d33304.jpg
2281 ms
product_top_SBR2-3.jpg
2100 ms
b78392a972fb4c7b80637ccb1844869d.jpg
2525 ms
696d416578c7baf0491242b33232abe3.jpg
2640 ms
fda8a1dbefd7e6a090f69d28b196df1e-1.jpg
2264 ms
8ca697e7483ee400ad1e8dda90978d27.jpg
2265 ms
2e07035e708f6e353a727c3bb179b81c-1.jpg
2429 ms
img-company01.jpg
2587 ms
img-company02.jpg
2442 ms
img-company03.jpg
2457 ms
img-company04.jpg
2592 ms
f439642b8bb0722d75f6ae7ef350b513.jpg
2605 ms
b65889e7a353d1bdcd6ffe2a2b0e5887-801x685.jpg
2633 ms
98853203ee908fbfff4bd3c780255410-980x685.png
3523 ms
font
84 ms
font
83 ms
icomoon.ttf
2412 ms
font
159 ms
hexadrive.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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
hexadrive.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
hexadrive.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 Hexadrive.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 Hexadrive.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.
hexadrive.jp
Open Graph data is detected on the main page of HEXADRIVE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: