9.1 sec in total
1.6 sec
7.4 sec
131 ms
Click here to check amazing Emtg content for Japan. Otherwise, check out these important facts you probably never knew about emtg.co.jp
株式会社Fanplusの公式サイト。ファンサイト・ファンクラブ、EC、生配信、オフィシャルサイト、アプリなど、アーティストとファンの架け橋となるインターネットサービスをご提供します。
Visit emtg.co.jpWe analyzed Emtg.co.jp page load time and found that the first response time was 1.6 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
emtg.co.jp performance score
name
value
score
weighting
Value9.5 s
0/100
10%
Value14.0 s
0/100
25%
Value15.7 s
0/100
10%
Value3,660 ms
1/100
30%
Value0.05
99/100
15%
Value14.2 s
9/100
10%
1583 ms
1022 ms
464 ms
1245 ms
5 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 79% of them (31 requests) were addressed to the original Emtg.co.jp, 5% (2 requests) were made to Maxcdn.bootstrapcdn.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Emtg.co.jp.
Page size can be reduced by 306.6 kB (29%)
1.0 MB
734.7 kB
In fact, the total size of Emtg.co.jp main page is 1.0 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. 25% of websites need less resources to load. Images take 626.8 kB which makes up the majority of the site volume.
Potential reduce by 15.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. This page needs HTML code to be minified as it can gain 2.7 kB, 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 15.7 kB or 77% of the original size.
Potential reduce by 6.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. Emtg images are well optimized though.
Potential reduce by 129.2 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 129.2 kB or 64% of the original size.
Potential reduce by 155.6 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. Emtg.co.jp needs all CSS files to be minified and compressed as it can save up to 155.6 kB or 82% of the original size.
Number of requests can be reduced by 14 (38%)
37
23
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Emtg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
emtg.co.jp
1583 ms
style.css
1022 ms
flexslider.css
464 ms
whhg.css
1245 ms
font-awesome.min.css
5 ms
jquery.min.js
32 ms
smoothScroll.js
396 ms
jquery.flexslider.js
1461 ms
jquery.tile.min.js
1380 ms
inquiry-form.css
1377 ms
jquery.js
2406 ms
ajaxzip2.js
1872 ms
jquery.upload.js
1771 ms
emtg.co.jp
2191 ms
emtg.co.jp
1874 ms
emtg.co.jp
1879 ms
ga.js
45 ms
logo_corp.jpg
515 ms
btn_menu_ticket.gif
437 ms
btn_menu_fanclub.gif
294 ms
btn_menu_fansite.gif
296 ms
btn_menu_emtg.gif
514 ms
btn_menu_app.gif
347 ms
btn_menu_media.gif
635 ms
bnr_e-ticket.gif
1147 ms
bnr_emtg.gif
800 ms
bnr_emtgmusic.gif
975 ms
bnr_recruit.jpg
1095 ms
bnr_top_ticket.jpg
1564 ms
bnr_top_fansite.jpg
1890 ms
bnr_top_fanclub.jpg
2050 ms
bnr_top_emtg.jpg
2444 ms
bnr_top_app.jpg
2449 ms
tag.js
8 ms
fontawesome-webfont.woff
24 ms
__utm.gif
11 ms
tag
12 ms
ya.js
368 ms
bg_direction_nav2.png
345 ms
emtg.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
Image elements do not have [alt] attributes
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>).
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.
emtg.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
emtg.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
Image elements do not have [alt] attributes
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 Emtg.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 Emtg.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.
emtg.co.jp
Open Graph description is not detected on the main page of Emtg. 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: