5.6 sec in total
1.3 sec
3.9 sec
335 ms
Welcome to 1923.co.jp homepage info - get ready to check 1923 best content for Japan right away, or after learning these important things about 1923.co.jp
スマートフォンアプリとスマートフォン向けゲームの企画、開発、運営を行うイグニスの公式ホームページです。イグニスのコーポレート情報、プロダクツ情報、採用情報、IR情報をご覧いただけます。
Visit 1923.co.jpWe analyzed 1923.co.jp page load time and found that the first response time was 1.3 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
1923.co.jp performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value32.4 s
0/100
25%
Value13.5 s
2/100
10%
Value470 ms
61/100
30%
Value0
100/100
15%
Value18.0 s
3/100
10%
1325 ms
313 ms
325 ms
353 ms
355 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 63% of them (43 requests) were addressed to the original 1923.co.jp, 10% (7 requests) were made to Apis.google.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain 1923.co.jp.
Page size can be reduced by 602.5 kB (18%)
3.3 MB
2.7 MB
In fact, the total size of 1923.co.jp main page is 3.3 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 42.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. 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 42.6 kB or 76% of the original size.
Potential reduce by 187.6 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. 1923 images are well optimized though.
Potential reduce by 194.0 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 194.0 kB or 67% of the original size.
Potential reduce by 178.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. 1923.co.jp needs all CSS files to be minified and compressed as it can save up to 178.3 kB or 83% of the original size.
Number of requests can be reduced by 35 (52%)
67
32
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1923. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
1923.co.jp
1325 ms
styles.css
313 ms
styles.css
325 ms
slimbox2.css
353 ms
lightbox.min.css
355 ms
jquery.js
891 ms
jquery-migrate.min.js
466 ms
slimbox2.js
475 ms
slimbox2_autoload.js
482 ms
wp-page-numbers.css
525 ms
reset.css
527 ms
bootstrap.min.css
1083 ms
font-awesome.css
4 ms
default.css
633 ms
style.css
962 ms
jquery.min.js
31 ms
bootstrap.min.js
872 ms
flexslider.css
552 ms
public.css
645 ms
jquery.form.min.js
903 ms
scripts.js
806 ms
scripts.js
900 ms
jquery.touchwipe.min.js
915 ms
jquery.lightbox.min.js
974 ms
jquery.flexslider-min.js
1137 ms
bookmark_button.js
316 ms
plusone.js
50 ms
analytics.js
22 ms
collect
12 ms
button-only@2x.png
160 ms
logo.png
177 ms
slide01-1498x477-1498x476.jpg
710 ms
slide02-1498x477-1498x476.jpg
639 ms
destroyer_icon_1024.png
1605 ms
2d6c2a8d2c7f3620cc8d0b847bf5a3ab.png
819 ms
67f6e43d8e8709aa6ced675aa4c4b7ba.png
540 ms
icon.png
1469 ms
56e932729ec6c019df977759d6c9281e.jpg
709 ms
87a4b38a53f3bde5c46c61ab86b5e2fe.png
774 ms
icon-512.png
1413 ms
icon_breaker-new.png
1769 ms
recruit_ceocto.png
1084 ms
btn_career.png
1139 ms
698659aea711eddfc1683bcda1222724.png
1394 ms
footTopic02.jpg
1302 ms
footTopic03.jpg
1463 ms
footTopic04.jpg
1550 ms
ignis_logo_rw.jpg
1588 ms
icon_target.gif
1612 ms
209 ms
sdk.js
178 ms
widgets.js
109 ms
cb=gapi.loaded_0
78 ms
cb=gapi.loaded_1
98 ms
fastbutton
159 ms
bg_direction_nav.png
1241 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
136 ms
postmessageRelay
73 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
35 ms
api.js
27 ms
core:rpc:shindig.random:shindig.sha1.js
79 ms
2536007149-postmessagerelay.js
56 ms
57 ms
xd_arbiter.php
158 ms
xd_arbiter.php
278 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
39 ms
jot
82 ms
1923.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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
1923.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
1923.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 1923.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 1923.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.
1923.co.jp
Open Graph description is not detected on the main page of 1923. 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: