6.9 sec in total
778 ms
5.4 sec
641 ms
Welcome to historia.co.jp homepage info - get ready to check Historia best content for Japan right away, or after learning these important things about historia.co.jp
ゲームの企画・開発・制作協力の株式会社ヒストリアです。UE4やVRの最先端技術を使ってPlayStation®4などのコンシューマーゲームやアーケードゲーム、デジタルコンテンツを創出し、人生観を変えるような体験を提供します。
Visit historia.co.jpWe analyzed Historia.co.jp page load time and found that the first response time was 778 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
historia.co.jp performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value15.6 s
0/100
25%
Value15.6 s
0/100
10%
Value590 ms
50/100
30%
Value0.304
39/100
15%
Value22.0 s
1/100
10%
778 ms
172 ms
340 ms
510 ms
522 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 98% of them (83 requests) were addressed to the original Historia.co.jp, 1% (1 request) were made to Kit.fontawesome.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Historia.co.jp.
Page size can be reduced by 767.6 kB (6%)
12.8 MB
12.0 MB
In fact, the total size of Historia.co.jp main page is 12.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 12.5 MB which makes up the majority of the site volume.
Potential reduce by 51.4 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 51.4 kB or 85% of the original size.
Potential reduce by 641.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. Historia images are well optimized though.
Potential reduce by 23.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 23.5 kB or 18% of the original size.
Potential reduce by 51.3 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. Historia.co.jp needs all CSS files to be minified and compressed as it can save up to 51.3 kB or 68% of the original size.
Number of requests can be reduced by 21 (25%)
83
62
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Historia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
historia.co.jp
778 ms
style.css
172 ms
slick.css
340 ms
index.css
510 ms
crayon.min.css
522 ms
style.min.css
525 ms
styles.css
524 ms
screen.min.css
524 ms
pagenavi-css.css
528 ms
jquery.fancybox.min.css
677 ms
jquery.min.js
870 ms
jquery-migrate.min.js
695 ms
crayon.min.js
697 ms
scripts.js
697 ms
front.min.js
697 ms
jquery.fancybox.min.js
844 ms
jquery.easing.min.js
867 ms
jquery.mousewheel.min.js
1053 ms
jquery.js
1065 ms
jquery.matchHeight.js
1054 ms
slick.js
1079 ms
common.js
1082 ms
91ff06b4f4.js
140 ms
gtm.js
330 ms
sp_link01.jpg
327 ms
sp_link02-new2.png
490 ms
logo.png
328 ms
h_link.gif
325 ms
h_link_sp-new.png
328 ms
h_search.jpg
329 ms
main_visual_new_01s.jpg
1160 ms
Richard_ContentSlider.png
1706 ms
f55446fe9acae1188c7dbc925a8853f3.png
1532 ms
main_visual_bg03.jpg
2060 ms
9b88b595266b342047d8e18015d738fd.png
1203 ms
line01.png
664 ms
1dd05cd9922c33d7408c8ce535bfcdbd-360x240.png
1190 ms
1dd05cd9922c33d7408c8ce535bfcdbd-600x400.png
1333 ms
Sep02_thumbnail_Logo_Blog-360x240.png
1720 ms
Sep02_thumbnail_Logo_Blog-600x400.png
1388 ms
FN_kv_game_thumbnail_1080_720-360x240.jpg
1505 ms
FN_kv_game_thumbnail_1080_720-600x400.jpg
1569 ms
bef96934b8c7cd23330548d9f35a8a37-360x240.png
1678 ms
bef96934b8c7cd23330548d9f35a8a37-600x400.png
1717 ms
85ca77e644ea2ed9d2cbab9604fa5eec-360x240.png
1748 ms
85ca77e644ea2ed9d2cbab9604fa5eec-600x400.png
1857 ms
arrow01.png
1879 ms
arrow02.png
1894 ms
d7f371d1d66800a49c5ce7daa37f3c99-270x180.jpg
1897 ms
d7f371d1d66800a49c5ce7daa37f3c99-600x400.jpg
1932 ms
4e0e50a3b4316230ed4ad39573536ada-270x180.jpg
2028 ms
4e0e50a3b4316230ed4ad39573536ada-600x400.jpg
2060 ms
7354a3975655704591e967398cfc754e-270x180.png
2069 ms
7354a3975655704591e967398cfc754e-600x400.png
2251 ms
778d6720e10698ae56750507e98db6ca-270x180.png
1976 ms
778d6720e10698ae56750507e98db6ca-600x400.png
2069 ms
Roboto-Medium.woff
2095 ms
1080_720-1-270x180.png
2080 ms
1080_720-1-600x400.png
1981 ms
4f8093490b0ad89e523f2a81aa728118-270x180.png
1990 ms
4f8093490b0ad89e523f2a81aa728118-600x400.png
2057 ms
bg04.jpg
2093 ms
sp_photo02.png
2095 ms
EyeCatch-360x240.png
2097 ms
EyeCatch-600x400.png
2105 ms
b1809651873581308cdab795c484f5d9.png
1975 ms
41df80bdd1ae239137bbdc47966a98cd-360x240.png
1889 ms
41df80bdd1ae239137bbdc47966a98cd-600x400.png
1441 ms
2024-07-12_17h46_50-360x240.jpg
1409 ms
2024-07-12_17h46_50-600x400.jpg
1397 ms
b1b128447f42de56d0516a0efb3d72d5-360x240.jpg
1279 ms
b1b128447f42de56d0516a0efb3d72d5-600x400.jpg
1256 ms
20e3bdb196ee179d0b63ec014e9268bb-360x240.png
1218 ms
20e3bdb196ee179d0b63ec014e9268bb-600x400.png
1245 ms
bg01.jpg
1205 ms
bg02.jpg
1099 ms
twitter_banner.jpg
1083 ms
TMOL-banner.png
1116 ms
page_top.png
1174 ms
f_bg02.jpg
1202 ms
sp_bg02.png
1094 ms
f_bg03.jpg
1072 ms
icon01.png
1069 ms
f_logo.png
1113 ms
sns_twitter.png
1131 ms
historia.co.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
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.
historia.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
historia.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
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 Historia.co.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 Historia.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.
historia.co.jp
Open Graph description is not detected on the main page of Historia. 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: