5 sec in total
470 ms
4.4 sec
140 ms
Welcome to enjing.jp homepage info - get ready to check ENJING best content for Japan right away, or after learning these important things about enjing.jp
Mr.Children、ナオト・インティライミが所属するプロダクション「エンジン」webサイト
Visit enjing.jpWe analyzed Enjing.jp page load time and found that the first response time was 470 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
enjing.jp performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value4.3 s
41/100
25%
Value10.5 s
7/100
10%
Value1,120 ms
23/100
30%
Value0
100/100
15%
Value15.5 s
7/100
10%
470 ms
261 ms
520 ms
536 ms
483 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 62% of them (24 requests) were addressed to the original Enjing.jp, 18% (7 requests) were made to Youtube.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Enjing.jp.
Page size can be reduced by 1.9 MB (84%)
2.2 MB
350.4 kB
In fact, the total size of Enjing.jp main page is 2.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 4.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. This page needs HTML code to be minified as it can gain 859 B, which is 13% 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 4.4 kB or 64% of the original size.
Potential reduce by 1.8 MB
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. Obviously, ENJING needs image optimization as it can save up to 1.8 MB or 95% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 50.6 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 50.6 kB or 20% of the original size.
Potential reduce by 14.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. Enjing.jp needs all CSS files to be minified and compressed as it can save up to 14.8 kB or 19% of the original size.
Number of requests can be reduced by 18 (53%)
34
16
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ENJING. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
enjing.jp
470 ms
www.enjing.jp
261 ms
www.enjing.jp
520 ms
normalize.css
536 ms
jquery.rbt-yt-box.css
483 ms
index.css
570 ms
modernizr-2.6.2.min.js
697 ms
jquery.min.js
28 ms
jquery.easing.1.3.js
551 ms
jquery.preloader.js
577 ms
plugins.js
1029 ms
jquery.rbt-yt-player.js
876 ms
jquery.rbt-yt-box.js
874 ms
main.js
1121 ms
js
70 ms
index_jsinit.css
1016 ms
engine_logo.png
1004 ms
btn_mrchildren202403.png
867 ms
btn_naoto2402.png
880 ms
btn_okubo2203.png
1126 ms
bnr_about.png
517 ms
bg2.png
516 ms
bg.png
879 ms
iframe_api
58 ms
www-widgetapi.js
4 ms
XXXXXXXX
67 ms
www-player.css
7 ms
www-embed-player.js
27 ms
base.js
55 ms
ad_status.js
137 ms
embed.js
42 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
41 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
46 ms
anime_logo.png
624 ms
id
22 ms
Create
26 ms
GenerateIT
15 ms
slide_btn.png
555 ms
slide_btn_current.png
474 ms
enjing.jp accessibility score
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
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.
enjing.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
Browser errors were logged to the console
enjing.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
![]()
JA
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enjing.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 Enjing.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.
enjing.jp
Open Graph data is detected on the main page of ENJING. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: