7 sec in total
31 ms
6.6 sec
360 ms
Welcome to toho-jp.net homepage info - get ready to check Toho Jp best content for Japan right away, or after learning these important things about toho-jp.net
東方神起の公式サイト。ライブ・イベント情報、メディア出演情報、CD・DVDのディスコグラフィー等。
Visit toho-jp.netWe analyzed Toho-jp.net page load time and found that the first response time was 31 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
toho-jp.net performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value9.9 s
0/100
25%
Value32.9 s
0/100
10%
Value32,020 ms
0/100
30%
Value0.94
3/100
15%
Value65.1 s
0/100
10%
31 ms
942 ms
50 ms
158 ms
216 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 27% of them (33 requests) were addressed to the original Toho-jp.net, 21% (26 requests) were made to Youtube.com and 13% (16 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Toho-jp.net.
Page size can be reduced by 421.7 kB (20%)
2.2 MB
1.7 MB
In fact, the total size of Toho-jp.net 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. 85% 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.4 MB which makes up the majority of the site volume.
Potential reduce by 32.0 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 32.0 kB or 78% of the original size.
Potential reduce by 471 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. Toho Jp images are well optimized though.
Potential reduce by 306.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 306.2 kB or 56% of the original size.
Potential reduce by 83.1 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. Toho-jp.net needs all CSS files to be minified and compressed as it can save up to 83.1 kB or 52% of the original size.
Number of requests can be reduced by 34 (40%)
86
52
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Toho Jp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
toho-jp.net
31 ms
toho-jp.net
942 ms
1
50 ms
gtm.js
158 ms
sift.css
216 ms
font-awesome.css
681 ms
jquery.fancybox.css
511 ms
slick-theme.css
512 ms
slick.css
216 ms
jquery.js
1187 ms
jquery.fancybox.js
1031 ms
heightLine.js
711 ms
smoothScroll.js
1025 ms
common.js
692 ms
css
153 ms
slick.min.js
1524 ms
copy.js
557 ms
copy.js
755 ms
widget
9 ms
zjctaM
65 ms
69 ms
destination
57 ms
uwt.js
28 ms
analytics.js
31 ms
basic.css
654 ms
sp.css
673 ms
NotoSansCJKjp.css
834 ms
collect
57 ms
adsct
148 ms
adsct
172 ms
copy.js
526 ms
widgets.js
281 ms
top_20220126_yunho-special.jpg
256 ms
top_20231018_livetour.jpg
1933 ms
top_20230612_newsingle.jpg
739 ms
top_20220930_livetour2023.jpg
1943 ms
top_20220317_fanclubevent2022.jpg
1933 ms
top_20220304_epitaph-special.jpg
638 ms
bnr_sm.jpg
640 ms
line.png
1931 ms
ico_el.png
1933 ms
top_20211129_human.jpg
297 ms
sdk.js
78 ms
gtm.js
133 ms
fbevents.js
85 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
219 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
236 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
267 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
280 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
280 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
280 ms
NotoSansCJKjp-SUBSET-R.woff
3219 ms
NotoSansCJKjp-SUBSET-M.woff
2365 ms
NotoSansCJKjp-SUBSET-L.woff
3626 ms
NotoSansCJKjp-SUBSET-Thin.woff
2486 ms
NotoSansCJKjp-SUBSET-B.woff
4235 ms
NotoSansCJKjp-SUBSET-BK.woff
4234 ms
jizaRExUiTo99u79D0KEwA.ttf
277 ms
jizfRExUiTo99u79B_mh0O6tKA.ttf
276 ms
gne1KJw-iL0
216 ms
G7HBBtMa_FA
274 ms
0X8lEvQXq1I
368 ms
vdec9LXFg-o
368 ms
ZwSxZviv9T4
367 ms
1255a5WarAU
366 ms
fontawesome-webfont.woff
2964 ms
sdk.js
57 ms
js
226 ms
collect
72 ms
collect
211 ms
www-player.css
151 ms
www-embed-player.js
150 ms
base.js
154 ms
ajax-loader.gif
2624 ms
www-embed-player.js
1 ms
gne1KJw-iL0
5 ms
G7HBBtMa_FA
4 ms
0X8lEvQXq1I
3 ms
vdec9LXFg-o
2 ms
ZwSxZviv9T4
2 ms
1255a5WarAU
1 ms
gne1KJw-iL0
224 ms
G7HBBtMa_FA
424 ms
0X8lEvQXq1I
443 ms
vdec9LXFg-o
336 ms
ZwSxZviv9T4
505 ms
1255a5WarAU
474 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
271 ms
text_plivacyPolicy.svg
1481 ms
copy_svg.min.css
1485 ms
text_sitePolicy.svg
1480 ms
text_avexlogo.svg
1477 ms
logo_avex_blue.png
1480 ms
ga-audiences
1487 ms
slick.woff
2771 ms
www-player.css
34 ms
www-embed-player.js
126 ms
base.js
299 ms
settings
1226 ms
ad_status.js
412 ms
jRYISRuM9q7e_xyYaLp_fsq3qnLjbNevd8JDa-bOkpI.js
217 ms
embed.js
147 ms
id
140 ms
Create
852 ms
Create
851 ms
Create
847 ms
Create
835 ms
Create
712 ms
Create
627 ms
Create
535 ms
Create
443 ms
Create
346 ms
Create
442 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
128 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
129 ms
GenerateIT
357 ms
GenerateIT
355 ms
GenerateIT
258 ms
GenerateIT
279 ms
GenerateIT
256 ms
GenerateIT
251 ms
toho-jp.net 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
[aria-*] attributes do not have valid values
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
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>).
toho-jp.net 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
Missing source maps for large first-party JavaScript
toho-jp.net 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Toho-jp.net 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 Toho-jp.net 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.
toho-jp.net
Open Graph data is detected on the main page of Toho Jp. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: