3.8 sec in total
322 ms
3.4 sec
84 ms
Click here to check amazing Imarine Project content for Russia. Otherwise, check out these important facts you probably never knew about imarine-project.jp
アイマリンプロジェクトオフィシャルサイト。アイマリンの最新情報を掲載。新生アイマリンプロジェクト、2019年12月より始動。
Visit imarine-project.jpWe analyzed Imarine-project.jp page load time and found that the first response time was 322 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
imarine-project.jp performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value10.9 s
0/100
25%
Value17.5 s
0/100
10%
Value25,160 ms
0/100
30%
Value1
2/100
15%
Value43.0 s
0/100
10%
322 ms
295 ms
293 ms
295 ms
772 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 86% of them (36 requests) were addressed to the original Imarine-project.jp, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Imarine-project.jp.
Page size can be reduced by 1.1 MB (80%)
1.4 MB
290.0 kB
In fact, the total size of Imarine-project.jp main page is 1.4 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. 20% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 9.8 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 3.0 kB, which is 24% 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 9.8 kB or 79% of the original size.
Potential reduce by 160 B
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. Imarine Project images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 83% of the original size.
Potential reduce by 16.8 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. Imarine-project.jp needs all CSS files to be minified and compressed as it can save up to 16.8 kB or 84% of the original size.
Number of requests can be reduced by 22 (55%)
40
18
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imarine Project. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
imarine-project.jp
322 ms
app.css
295 ms
slick.css
293 ms
eventemitter3.js
295 ms
jquery.min.js
772 ms
jquery.easing.1.3.js
296 ms
easeljs-0.8.1.min.js
738 ms
tweenjs-0.6.1.min.js
582 ms
howler.min.js
436 ms
slick.min.js
581 ms
pixi.js
2218 ms
all.js
1327 ms
conversion.js
71 ms
analytics.js
25 ms
50 ms
footer_map_btn.png
294 ms
twitter_btn.png
309 ms
twitter_btn1_animation.png
310 ms
facebook_btn.png
310 ms
facebook_btn1_animation.png
311 ms
googleplus_btn.png
311 ms
googleplus_btn1_animation.png
427 ms
sound_btn_text.png
455 ms
footer_line.png
458 ms
top_btn_text.png
457 ms
concept_btn_text.png
458 ms
members_btn_text.png
457 ms
member_btn_06_text.png
578 ms
member_btn_05_text.png
603 ms
member_btn_04_text.png
602 ms
member_btn_03b_text.png
603 ms
member_btn_02_text.png
603 ms
member_btn_01_text.png
603 ms
music_btn_text.png
723 ms
character_btn_text.png
759 ms
footer_new_mark.png
759 ms
dance_btn_text.png
759 ms
twitter_btn_text.png
756 ms
footer_copyright.png
759 ms
collect
18 ms
33 ms
iframe_api
25 ms
imarine-project.jp accessibility score
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
imarine-project.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
imarine-project.jp SEO score
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 doesn't use 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 Imarine-project.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 Imarine-project.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.
imarine-project.jp
Open Graph description is not detected on the main page of Imarine Project. 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: