8.4 sec in total
1.1 sec
6.3 sec
1 sec
Welcome to forthenext.jp homepage info - get ready to check FOR THE NEXT best content for Japan right away, or after learning these important things about forthenext.jp
5つのFMラジオ局が各地のネクストブレイクアーティストを紹介する「FOR THE NEXT」。テーマソングはBE:FIRST「Brave Generation」
Visit forthenext.jpWe analyzed Forthenext.jp page load time and found that the first response time was 1.1 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
forthenext.jp performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value6.9 s
6/100
25%
Value9.2 s
13/100
10%
Value850 ms
33/100
30%
Value0.012
100/100
15%
Value7.0 s
53/100
10%
1078 ms
318 ms
503 ms
514 ms
1465 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 81% of them (102 requests) were addressed to the original Forthenext.jp, 6% (8 requests) were made to Apis.google.com and 2% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Forthenext.jp.
Page size can be reduced by 277.8 kB (11%)
2.5 MB
2.2 MB
In fact, the total size of Forthenext.jp main page is 2.5 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. 50% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 33.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. 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 33.5 kB or 73% of the original size.
Potential reduce by 125.8 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. FOR THE NEXT images are well optimized though.
Potential reduce by 109.5 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 109.5 kB or 64% of the original size.
Potential reduce by 8.9 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. Forthenext.jp needs all CSS files to be minified and compressed as it can save up to 8.9 kB or 79% of the original size.
Number of requests can be reduced by 18 (15%)
124
106
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FOR THE NEXT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
forthenext.jp
1078 ms
reset.css
318 ms
common.css
503 ms
index3.css
514 ms
jquery-1.9.1.min.js
1465 ms
jquery.easing.1.3.js
552 ms
ftn.js
631 ms
jfl.js
670 ms
smoothscroll.js
683 ms
putSocialFeeds.js
560 ms
bg.jpg
1576 ms
ph_yentownband.jpg
255 ms
livefornext.png
397 ms
detail.gif
251 ms
ph_northwave3.png
513 ms
senkou4-2.jpg
357 ms
ph_jwave3.png
681 ms
senkou_j3.jpg
392 ms
ph_zipfm3.png
870 ms
senkou5-2.jpg
576 ms
ph_fm8023.png
778 ms
senkou2-2.jpg
686 ms
ph_crossfm4.png
772 ms
senkou3-2.jpg
843 ms
bnr_elecom.png
857 ms
scene01.jpg
975 ms
sapporo.gif
980 ms
lv_yentownband_s.png
1006 ms
lv_asidman_s.png
1201 ms
lv_lily_s.png
1042 ms
ticket1.png
1156 ms
tokyo.png
1162 ms
lv_amazarashi_s.png
1335 ms
nagoya.gif
1212 ms
lv_miwa_s.png
1352 ms
lv_fujimaki_s.png
1551 ms
osaka.gif
1376 ms
lv_yentownband.png
1567 ms
lv-osaka.png
1654 ms
fukuoka.gif
1548 ms
lv_creep_s.png
1718 ms
northwave.gif
1736 ms
radio_northwave_1.png
2140 ms
radio_northwave_2.png
1787 ms
radio_northwave_3.png
1924 ms
sdk.js
17 ms
radio_northwave_4.png
1981 ms
widgets.js
96 ms
plusone.js
92 ms
190 ms
xd_arbiter.php
34 ms
xd_arbiter.php
42 ms
cb=gapi.loaded_0
93 ms
analytics.js
43 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
126 ms
cb=gapi.loaded_1
12 ms
fastbutton
71 ms
radio_northwave_5.png
1824 ms
radio_northwave_6.png
1857 ms
collect
33 ms
postmessageRelay
49 ms
cb=gapi.loaded_0
24 ms
cb=gapi.loaded_1
34 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
50 ms
like.php
101 ms
3193398744-postmessagerelay.js
30 ms
rpc:shindig_random.js
33 ms
jwave.gif
1623 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
47 ms
cb=gapi.loaded_0
3 ms
radio_jwave_1.png
1891 ms
radio_jwave_2.png
1802 ms
wy1X4hBW7e7.js
47 ms
LVx-xkvaJ0b.png
15 ms
radio_jwave_3.png
1823 ms
jot
87 ms
radio_jwave_4.png
1845 ms
radio_jwave_5.png
1811 ms
radio_jwave_6.png
1850 ms
zipfm.gif
1609 ms
radio_zipfm_1.png
1872 ms
radio_zipfm_2.png
1821 ms
radio_zipfm_3.png
1727 ms
radio_zipfm_4.png
1925 ms
radio_zipfm_5.png
1893 ms
radio_zipfm_6.png
1933 ms
fm802.gif
1760 ms
radio_fm802_1.png
1803 ms
radio_fm802_2.png
1701 ms
radio_fm802_3.png
1836 ms
radio_fm802_4.png
1787 ms
radio_fm802_5.png
1840 ms
radio_fm802_6.png
1886 ms
crossfm.gif
1719 ms
radio_crossfm_1.png
1914 ms
radio_crossfm_2.png
1637 ms
radio_crossfm_3.png
1649 ms
radio_crossfm_4.png
1692 ms
radio_crossfm_5.png
1719 ms
radio_crossfm_6.png
1726 ms
backtotop.png
1654 ms
jfl.gif
1643 ms
copyrights.gif
1641 ms
titlelogo.png
1578 ms
ar-2015.png
1547 ms
lead.png
1798 ms
japan.png
1508 ms
ar-song.png
1467 ms
carradio.png
1525 ms
ar-event.png
1487 ms
ar_next_artist.png
1428 ms
area-northwave2.png
1409 ms
area-jwave2.png
1381 ms
area-zipfm2.png
1434 ms
area-fm8022.png
1392 ms
area-crossfm2.png
1366 ms
line-radiosp-prg.png
1323 ms
tt-spradio.png
1286 ms
line-audition.png
1302 ms
titlelogo-m.png
1439 ms
tt-audition1.png
1281 ms
line-live.png
1240 ms
tt-live1.png
1221 ms
line-radio.png
1237 ms
titlelogo-m3.png
1259 ms
tt-radio1.png
1268 ms
forthenext.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
forthenext.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
forthenext.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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forthenext.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 Forthenext.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.
forthenext.jp
Open Graph data is detected on the main page of FOR THE NEXT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: