6.5 sec in total
512 ms
5.5 sec
514 ms
Click here to check amazing Tag content for Japan. Otherwise, check out these important facts you probably never knew about tag.co.jp
声優・漫画・アニメ業界でプロを目指す方専門の学校「東京アニメーター学院」東アニの特色と学科・入学 案内。体験入学の日程・お申し込み、入学案内書(無料)の資料請求などのご案内。
Visit tag.co.jpWe analyzed Tag.co.jp page load time and found that the first response time was 512 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tag.co.jp performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value13.4 s
0/100
25%
Value18.6 s
0/100
10%
Value900 ms
32/100
30%
Value0.003
100/100
15%
Value17.9 s
3/100
10%
512 ms
671 ms
337 ms
677 ms
354 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 57% of them (77 requests) were addressed to the original Tag.co.jp, 15% (20 requests) were made to Static.xx.fbcdn.net and 5% (7 requests) were made to Calendar.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Tag.co.jp.
Page size can be reduced by 292.5 kB (23%)
1.3 MB
972.7 kB
In fact, the total size of Tag.co.jp main page is 1.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. 45% of websites need less resources to load. Images take 849.3 kB which makes up the majority of the site volume.
Potential reduce by 23.5 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 4.0 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 23.5 kB or 74% of the original size.
Potential reduce by 26.5 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. Tag images are well optimized though.
Potential reduce by 170.7 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 170.7 kB or 57% of the original size.
Potential reduce by 71.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. Tag.co.jp needs all CSS files to be minified and compressed as it can save up to 71.8 kB or 84% of the original size.
Number of requests can be reduced by 60 (46%)
131
71
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tag. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
tag.co.jp
512 ms
www.tag.co.jp
671 ms
DD_belatedPNG.js
337 ms
common.css
677 ms
column-2.css
354 ms
course.css
527 ms
swfobject_modified.js
549 ms
rollover.js
241 ms
navi_on.js
352 ms
ga.js
6 ms
second_third_body_bg.gif
171 ms
get_flash_player.gif
29 ms
__utm.gif
29 ms
second-third_bg.gif
355 ms
other_bg.gif
210 ms
wrapper_bg.png
212 ms
logo.gif
210 ms
group2.gif
211 ms
unavi_start.gif
334 ms
unavi_01.gif
362 ms
unavi_02.gif
363 ms
unavi_end.gif
386 ms
gnavi_bg.png
421 ms
i_img_01.jpg
505 ms
ariaAA.jpg
1127 ms
mysteria.jpg
1665 ms
i_voice_img_01.jpg
543 ms
i_voice_img_02.jpg
572 ms
i_comic_img_01.jpg
612 ms
i_comic_img_04.jpg
706 ms
i_animetion_img_01.jpg
734 ms
i_animetion_img_03.jpg
745 ms
i_illust_img_01.jpg
803 ms
i_illust_img_03.jpg
875 ms
support_bnr_free_large.gif
905 ms
sub_btn_guide.png
1105 ms
pdf_icon_02.png
1003 ms
benefit_h.gif
1042 ms
benefit_img.jpg
1084 ms
challenge_btn.gif
1208 ms
challenge_tel.gif
1216 ms
mobile_h.gif
1255 ms
qr_tokyo.gif
1292 ms
banner_01_foot.gif
1301 ms
banner_blog.gif
1414 ms
banner_twitter.png
1402 ms
banner_line.png
1427 ms
FaceBook-icon.png
1497 ms
all.js
160 ms
embed
59 ms
embed
132 ms
tag.js
208 ms
Youtube-icon.png
1348 ms
mobile_h2.gif
1394 ms
bnr_h_02.gif
1403 ms
bnr_b_02.gif
1417 ms
979b49df4ebf2506acdc41045b4c0329embedcompiled_fastui.css
8 ms
979b49df4ebf2506acdc41045b4c0329embedcompiled__en.js
18 ms
client.js
46 ms
banner_btn_01.gif
1485 ms
131 ms
xd_arbiter.php
137 ms
xd_arbiter.php
251 ms
cb=gapi.loaded_0
14 ms
postmessageRelay
42 ms
tag
17 ms
bnr_h_03.gif
1359 ms
3193398744-postmessagerelay.js
21 ms
rpc:shindig_random.js
29 ms
banner_btn_02.gif
1432 ms
pagetop.gif
1448 ms
i_h2_bg.gif
1437 ms
cb=gapi.loaded_0
3 ms
logo-plus.png
29 ms
googlelogo_color_46x16dp.png
31 ms
proxy.html
47 ms
blank.gif
16 ms
menu_arrow_open.gif
7 ms
combined_v22.png
19 ms
course_icon.gif
1460 ms
course_dt_bg_01.gif
1455 ms
cb=gapi.loaded_0
2 ms
events
79 ms
course_dt_bg_02.gif
1383 ms
course_dt_bg_03.gif
1417 ms
course_dt_bg_04.gif
1421 ms
course_dt_bg_08.gif
1400 ms
sub_navi_bg.gif
1351 ms
challenge_bottom.gif
1321 ms
mobile_bg.gif
1323 ms
pagetop_o.gif
1329 ms
bnr_bg_02.gif
1289 ms
bnr_bg_03.gif
1298 ms
listmark_footmenu.gif
1223 ms
conversion_async.js
35 ms
group2_o.gif
171 ms
unavi_01_o.gif
182 ms
unavi_02_o.gif
174 ms
support_bnr_free_large_o.gif
202 ms
sub_btn_guide_o.png
185 ms
challenge_btn_o.gif
198 ms
banner_blog_o.gif
352 ms
banner_twitter_o.png
365 ms
banner_btn_01_o.gif
372 ms
banner_btn_02_o.gif
371 ms
28 ms
26 ms
34 ms
30 ms
like_box.php
156 ms
wIQ5cz_qN26.css
174 ms
OAknSm1a3Ik.css
216 ms
rq28xVeqcvr.css
259 ms
2qKTn8PrC5S.css
323 ms
R3qW8mZR52t.css
332 ms
q68gy-v_YMF.js
330 ms
ehA1CqzHyzE.js
375 ms
0wM5s1Khldu.js
315 ms
1bNoFZUdlYZ.js
296 ms
njO1TPvGzoR.js
362 ms
1QuX41zDRrx.js
362 ms
Oagsvfb4VWi.js
395 ms
LTv6ZK-5zxz.js
489 ms
1FCa-btixu2.js
410 ms
10393681_1169351509747707_2054897686644107800_n.png
489 ms
safe_image.php
257 ms
11745502_1169351419747716_7984765801614209812_n.png
523 ms
12651256_1284442698238587_5350203586688271848_n.jpg
561 ms
12642954_1275099892506201_2196911797061527752_n.jpg
678 ms
12552842_1275098389173018_2090714210076317417_n.jpg
639 ms
wL6VQj7Ab77.png
139 ms
s7jcwEQH7Sx.png
139 ms
QDwYpIaRyfG.png
138 ms
K00K-UgnsKu.png
138 ms
I6-MnjEovm5.js
43 ms
pQrUxxo5oQp.js
83 ms
tag.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 toggle fields do not have accessible names
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
tag.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
tag.co.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 uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tag.co.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 Tag.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.
tag.co.jp
Open Graph description is not detected on the main page of Tag. 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: