9.4 sec in total
726 ms
7.8 sec
836 ms
Welcome to harajuku-estage.jp homepage info - get ready to check Harajuku Estage best content for Japan right away, or after learning these important things about harajuku-estage.jp
原宿の玄関、竹下通りにオープンした「原宿駅前ステージ」。光るランウェイが常設されたプレミアムなステージに、デビューを夢見るフレッシュな女のコたちが登場!
Visit harajuku-estage.jpWe analyzed Harajuku-estage.jp page load time and found that the first response time was 726 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
harajuku-estage.jp performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value8.7 s
1/100
25%
Value7.6 s
26/100
10%
Value220 ms
87/100
30%
Value0
100/100
15%
Value8.7 s
36/100
10%
726 ms
480 ms
502 ms
1353 ms
677 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 32% of them (43 requests) were addressed to the original Harajuku-estage.jp, 10% (14 requests) were made to Google.com and 10% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Harajuku-estage.jp.
Page size can be reduced by 1.1 MB (7%)
16.1 MB
14.9 MB
In fact, the total size of Harajuku-estage.jp main page is 16.1 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. 75% 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 14.5 MB which makes up the majority of the site volume.
Potential reduce by 23.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. 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 23.7 kB or 72% of the original size.
Potential reduce by 45.9 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. Harajuku Estage images are well optimized though.
Potential reduce by 839.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 839.5 kB or 66% of the original size.
Potential reduce by 226.0 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. Harajuku-estage.jp needs all CSS files to be minified and compressed as it can save up to 226.0 kB or 82% of the original size.
Number of requests can be reduced by 55 (45%)
121
66
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Harajuku Estage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
harajuku-estage.jp
726 ms
reset.css
480 ms
style.css
502 ms
jquery-1.10.1.min.js
1353 ms
jquery.bxslider.min.js
677 ms
platform.js
58 ms
jquery.easing.1.3.js
159 ms
respond.min.js
475 ms
jquery.slidescroll.js
318 ms
jquery.backstretch.min.js
486 ms
common.js
356 ms
conversion.js
15 ms
header_title.png
662 ms
main01.jpg
2915 ms
main02.jpg
3254 ms
main03.jpg
3179 ms
main04.jpg
3375 ms
main05.jpg
3377 ms
main06.jpg
3378 ms
main07.jpg
4037 ms
main08.jpg
4535 ms
main09.jpg
4092 ms
bnr_hulu.png
3544 ms
bnr_goods.jpg
4220 ms
sns_tw_stage.png
4370 ms
sns_tw_parties.png
3713 ms
LINE_icon_Black.png
3883 ms
sns_lineblog.png
4051 ms
fuwafuwa600.jpg
4357 ms
harajukuotome.jpg
4224 ms
haraekistagea.jpg
4259 ms
pinkdiamond_shusei.jpg
5997 ms
button04.png
4390 ms
schedule.png
4426 ms
stage.png
5351 ms
access.png
4683 ms
button02.png
4559 ms
logo.png
4594 ms
twitter_logo_black.png
4699 ms
sdk.js
422 ms
Ys5CXiP4RSg
141 ms
widgets.js
56 ms
FJ0lBtRQ4NI
138 ms
embed
136 ms
embed
247 ms
www-embed-player-vflQrT_sR.css
87 ms
www-embed-player.js
122 ms
base.js
162 ms
analytics.js
50 ms
146 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
102 ms
embed
269 ms
header_bg.jpg
4527 ms
header_bg2.jpg
4560 ms
header_bg3.jpg
4641 ms
header_bg4.jpg
4668 ms
header_bg5.jpg
4696 ms
header_bg6.jpg
4726 ms
collect
64 ms
syndication
266 ms
636482880697270273
343 ms
js
228 ms
init_embed.js
197 ms
118 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
69 ms
ad_status.js
174 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
160 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
181 ms
f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled_fastui.css
100 ms
f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled__en.js
126 ms
client.js
101 ms
182 ms
xd_arbiter.php
358 ms
xd_arbiter.php
591 ms
cb=gapi.loaded_0
9 ms
postmessageRelay
185 ms
common.js
65 ms
map.js
175 ms
google4.png
148 ms
overlay.js
236 ms
2728.png
269 ms
util.js
240 ms
onion.js
265 ms
search_impl.js
264 ms
1f493.png
260 ms
1f60b.png
260 ms
1f46f.png
260 ms
1f601.png
262 ms
1f4ad.png
259 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
21 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
111 ms
api.js
161 ms
core:rpc:shindig.random:shindig.sha1.js
251 ms
2536007149-postmessagerelay.js
248 ms
J6XNFJsb_normal.png
237 ms
OyaiiDIM_normal.png
342 ms
stats.js
104 ms
openhand_8_8.cur
95 ms
ViewportInfoService.GetViewportInfo
227 ms
controls.js
73 ms
logo-plus.png
185 ms
googlelogo_color_46x16dp.png
255 ms
proxy.html
218 ms
blank.gif
152 ms
menu_arrow_open.gif
152 ms
combined_v22.png
182 ms
transparent.png
160 ms
css
251 ms
entity11.png
183 ms
jot
104 ms
mapcnt6.png
96 ms
sv5.png
130 ms
ViewportInfoService.GetViewportInfo
66 ms
kh
161 ms
kh
159 ms
tmapctrl.png
115 ms
vt
173 ms
vt
156 ms
vt
127 ms
vt
140 ms
vt
149 ms
vt
159 ms
vt
168 ms
vt
182 ms
vt
226 ms
vt
283 ms
cb=gapi.loaded_0
32 ms
ViewportInfoService.GetViewportInfo
59 ms
events
207 ms
events
105 ms
events
76 ms
events
61 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
5 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
10 ms
AuthenticationService.Authenticate
15 ms
harajuku-estage.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Form elements do not have associated labels
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
harajuku-estage.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
harajuku-estage.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 uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Harajuku-estage.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 Harajuku-estage.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.
harajuku-estage.jp
Open Graph description is not detected on the main page of Harajuku Estage. 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: