97.7 sec in total
732 ms
47.5 sec
49.5 sec
Welcome to joinalive.jp homepage info - get ready to check JOIN ALIVE best content for Japan right away, or after learning these important things about joinalive.jp
マウントアライブがプロデュースする野外フェス JOIN ALIVE 2024(ジョインアライブ2024)公式サイト。2024年7月13日(土)14日(日)北海道岩見沢にて開催!
Visit joinalive.jpWe analyzed Joinalive.jp page load time and found that the first response time was 732 ms and then it took 96.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 39 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
joinalive.jp performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value12.1 s
0/100
25%
Value10.7 s
7/100
10%
Value230 ms
86/100
30%
Value0.098
90/100
15%
Value14.7 s
8/100
10%
732 ms
1332 ms
386 ms
1135 ms
1133 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 36% of them (53 requests) were addressed to the original Joinalive.jp, 26% (38 requests) were made to D3e25kotnzlv99.cloudfront.net and 7% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (21 sec) relates to the external source Platform.twitter.com.
Page size can be reduced by 2.3 MB (24%)
9.3 MB
7.0 MB
In fact, the total size of Joinalive.jp main page is 9.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. Only a small number of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.
Potential reduce by 27.3 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 27.3 kB or 70% of the original size.
Potential reduce by 394.6 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. JOIN ALIVE images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 64% of the original size.
Potential reduce by 580.7 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. Joinalive.jp needs all CSS files to be minified and compressed as it can save up to 580.7 kB or 82% of the original size.
Number of requests can be reduced by 41 (44%)
94
53
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JOIN ALIVE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
732 ms
css
1332 ms
notosansjapanese.css
386 ms
font-awesome.min.css
1135 ms
common.css
1133 ms
jquery.fancybox-1.3.4.css
1164 ms
jquery.bxslider.css
1277 ms
prettyPhoto.css
1615 ms
page.css
1404 ms
analytics.js
1133 ms
autotrack.js
1177 ms
widgets.js
1268 ms
widgets.js
960 ms
index.js
1268 ms
jquery-1.10.1.min.js
2256 ms
global-menu.js
1267 ms
scrollsmoothly.js
1960 ms
global-menu_top.js
1961 ms
org_top.js
1960 ms
fp.js
627 ms
addfriends_ja.png
1202 ms
logo1.png
535 ms
logo2.png
826 ms
date.png
827 ms
h_tw.png
828 ms
h_fb.png
826 ms
h_ln.png
812 ms
h_yt.png
1240 ms
h_ct.png
1240 ms
show_more.png
1240 ms
wj.jpg
4402 ms
ip.png
1272 ms
jtb.png
1273 ms
social_tw.png
1273 ms
social_fb.png
1273 ms
social_yt.png
1578 ms
social_fd.png
1579 ms
social_line.png
1881 ms
mmm.png
1879 ms
sapporo.png
1879 ms
jcb.png
4354 ms
lawson.png
4353 ms
hmv.png
4969 ms
logos.png
4968 ms
ma.png
5064 ms
collect
642 ms
all.js
478 ms
20170716214925_1.png
5381 ms
collect
1110 ms
header_line.png
4074 ms
20170825171422_1.png
3939 ms
20170825171736_1.png
4781 ms
20170721165627_1.jpg
3875 ms
20170711202434_1.png
3662 ms
QuZMU9THSNo
3536 ms
l_t_square.png
3334 ms
r_b_square.png
3333 ms
SL0aFUFfkFMMdariYQ3_YZ0EAVxt0G0biEntp43Qt6E.ttf
11819 ms
fontawesome-webfont.woff
5157 ms
offsite_event.php
10083 ms
www-player-vflMqr8uC.css
1311 ms
www-embed-player.js
7151 ms
base.js
10657 ms
embed
10216 ms
a_arrow.png
6735 ms
artist_bg.png
6734 ms
ticket_top_bg.png
6734 ms
ticket_bottom_bg.png
7976 ms
access_bg.png
9077 ms
a_arrow_s.png
8815 ms
NotoSansJP-Regular.woff
7689 ms
NotoSansJP-Medium.woff
8793 ms
NotoSansJP-DemiLight.woff
9409 ms
NotoSansJP-Light.woff
9409 ms
NotoSansJP-Thin.woff
9409 ms
NotoSansJP-Bold.woff
9408 ms
NotoSansJP-Black.woff
9407 ms
8545 ms
iKtt7hEgWoINE3ULg26iBJzYy
7655 ms
0sTQzbapM8j.js
6292 ms
0sTQzbapM8j.js
20483 ms
uh.js
10098 ms
plusone.js
20446 ms
ping
6381 ms
timeline.bc7ee675e57cb01f4d1e255156414e73.js
20998 ms
button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js
20734 ms
reset-3.3.0.css
19586 ms
jquery-ui-1.10.3.custom.min-2b9eaeb9e58acce1d889b97baefa5fe439ad611d796f04f3f7cdbbfb49efcd11.css
19586 ms
jquery-ui-1.10.3.custom.org-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.css
19586 ms
jquery.pnotify.default-30db19eb64f0fc55cd5991e5de6986ccca99fa5ab7428e38eed1e0d3e7140d36.css
19586 ms
jquery.pnotify.default.icons-8f8f88178bfbfa1856e53ce5a8e5a7886335c73d9ab3e48b457bec1190496ef6.css
19541 ms
jquery.pnotify.custom.org-e30aa185e766023ba87e91cf004e6d87f3e25cbc31ef5e1d8dc4597da8cb423f.css
19540 ms
application-e3d0b60293f530448571070528894c0462da66404d7f3150bb1fde5b8ec1f5de.css
19540 ms
base-142662370504843549781a7f556442c8391d756b09512ad3be2ef0137c4d1a94.css
19541 ms
css
5318 ms
application-de299f1b3ccfcebdb3df6c346cfc01c889242fe6732b04d223627fbc269de41a.css
19530 ms
navigation-5ce76fa0fe8b23826e9520116100d01f03b9d19c53475e818f355b1696d5fe96.css
0 ms
spheres_desktop-7a36b22924dd0452f6fee6d6b0bb411426647ce602cadcc3c4065f7377b3906c.css
0 ms
jquery-2.2.4.min.js
0 ms
jquery.preload.min.js
0 ms
jquery.cookie-1.3.1.min.js
20864 ms
jquery.mousewheel-3.0.6.min.js
20864 ms
jquery.maxlength-1.2.min.js
20865 ms
jquery.ah-placeholder-1.2.min.js
20865 ms
jquery.textchange_20100604.min.js
20864 ms
jquery.ba-outside-events-1.1.min.js
20864 ms
jquery-ui-1.10.3.custom.min-5bc386117404b25755a7867e068d7fec3537a36d85c5f32325256b01f61b5cc6.js
20864 ms
jquery.pnotify.min-e16c22dce80a94cf005403afc83e1d69fe1d045e80a27fd5967222554e4f21b7.js
20863 ms
jquery.fullscreen-1.1.5.min.js
20864 ms
application-b4598c6e9285ffbcbb5ffb99cc26e709b082b30a9c156b9177866f21be054b95.js
20864 ms
application-40dc084e2143d40e736f125e23faca2529771ef3b960cfe53ef5200b2edb7e4c.js
20815 ms
three-85.min.js
20860 ms
three-73.projector.min.js
20860 ms
three-73.canvas_renderer.min.js
20860 ms
sphere_viewer_camera_fov_adjuster-cc749aa22b02f0c98e976b56bfb57bc353a259e116d21bec694389ec8a459442.js
20860 ms
sphere_viewer-2c922c5e6b93d3354e8c092303d09594e39f3a62b32f0b56c4dac66d58159071.js
20860 ms
sphere_viewer_desktop-009c9a69019ca5bb8ff1f694e99ca6b13dc0dd37b013451f1d8f6aaeaeac6515.js
20860 ms
spheres_show-819979b945e487be7dee241ee403c4438bd0d00b4493cb59ee60d5afb7c743de.js
20859 ms
jquery_ujs-1.2.1.min.js
20859 ms
analytics-30e55ad92cd162da4da3c3b083dfe56af87e6fd6ef37b0676fe020e1040076f8.js
20860 ms
share_button.php
15273 ms
js
0 ms
init_embed.js
0 ms
print.css
15139 ms
id
10619 ms
YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js
11998 ms
ad_status.js
17071 ms
e-ZFKNOPjyX.js
7267 ms
watermark_ringo-vflPWbiPS.png
6495 ms
uPlIYLfynqH.png
9643 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
3623 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
3975 ms
jot
6444 ms
gtm.js
5523 ms
in_progress_animation-b41a9500745611618e79fd2c9189270f46f955ac1d7ba65f6bae39887b736088.gif
4918 ms
logo_embed-04c973443446001ff5cb26cb5f05783cd37ce3ba079c688575e0da23f5fb2d9c.png
4917 ms
btn_plus_normal-d980d21a9f5f9869893e55d62632f2225f77c01d2f5f94fb26959ce8a9377140.png
5245 ms
btn_minus_normal-5fcbd464b1fb2b9b9e6f4649ca868f34a036b828f97823a38aa53e561b00dcf9.png
5085 ms
reset_normal-fae66edb2e266039cec36e70a9cd7d7195b0c10081092d39513bc40c0c32e031.png
5084 ms
common.js
1026 ms
map.js
1027 ms
google4.png
308 ms
overlay.js
305 ms
util.js
149 ms
onion.js
82 ms
search_impl.js
250 ms
stats.js
170 ms
joinalive.jp accessibility score
joinalive.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
Page has valid source maps
joinalive.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Joinalive.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 Joinalive.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.
joinalive.jp
Open Graph data is detected on the main page of JOIN ALIVE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: