12.1 sec in total
1.5 sec
10 sec
559 ms
Click here to check amazing Reina Park content. Otherwise, check out these important facts you probably never knew about reina-park.com
本当の体力足りていますか?バランスボールを使ったレッスンで真の体力をつける、ココロとカラダのメンテナンススタジオ|スタジオレイナパーク
Visit reina-park.comWe analyzed Reina-park.com page load time and found that the first response time was 1.5 sec and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
reina-park.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value7.6 s
3/100
25%
Value9.6 s
11/100
10%
Value590 ms
50/100
30%
Value0.199
62/100
15%
Value15.8 s
6/100
10%
1505 ms
1021 ms
851 ms
525 ms
6 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 56% of them (80 requests) were addressed to the original Reina-park.com, 15% (21 requests) were made to Maps.googleapis.com and 11% (16 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Reina-park.com.
Page size can be reduced by 2.3 MB (44%)
5.2 MB
2.9 MB
In fact, the total size of Reina-park.com main page is 5.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. 65% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 34.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 34.5 kB or 73% of the original size.
Potential reduce by 1.4 MB
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. Obviously, Reina Park needs image optimization as it can save up to 1.4 MB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 556.1 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 556.1 kB or 69% of the original size.
Potential reduce by 340.5 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. Reina-park.com needs all CSS files to be minified and compressed as it can save up to 340.5 kB or 70% of the original size.
Number of requests can be reduced by 36 (26%)
138
102
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reina Park. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
reina-park.com
1505 ms
style.css
1021 ms
hover-min.css
851 ms
flexslider.css
525 ms
jquery.min.js
6 ms
heightLine.js
541 ms
boxMouseover.js
376 ms
jquery.page-scroller.js
751 ms
jquery.flexslider.min.js
1048 ms
ai1ec_parsed_css.css
1897 ms
pagenavi-css.css
558 ms
platform.js
66 ms
wp-embed.min.js
401 ms
wp-emoji-release.min.js
677 ms
sdk.js
277 ms
analytics.js
101 ms
embed
265 ms
embed
307 ms
ico_arw.gif
706 ms
h_logo.gif
258 ms
h_btn_reserved_on.gif
384 ms
h_btn_reserved.gif
498 ms
h_bnr_top.jpg
754 ms
h_bnr_tel.gif
680 ms
bg_nav.gif
464 ms
h_ico_nav_off.gif
679 ms
bg_top_01.jpg
1320 ms
img_slide_01.jpg
2282 ms
img_slide_02.jpg
1867 ms
img_slide_03.jpg
1336 ms
img_slide_04.jpg
2117 ms
h_img_apple.png
1093 ms
h_img_lesson.png
3322 ms
ico_lesson.gif
1489 ms
img_lesson_01.jpg
1833 ms
img_lesson_02.jpg
2512 ms
img_lesson_03.jpg
2164 ms
ico_arw_btn_off.png
2035 ms
img_slide_lesson_01.jpg
3055 ms
img_slide_lesson_02.jpg
2977 ms
img_slide_lesson_03.jpg
2987 ms
img_slide_lesson_04.jpg
3446 ms
bg.jpg
3531 ms
img_top_01.jpg
3655 ms
img_melit_01.jpg
3317 ms
img_melit_02.jpg
4262 ms
img_melit_03.jpg
3811 ms
img_melit_04.jpg
4228 ms
lesson01_img_05.png
3952 ms
lesson01_img_07.png
3922 ms
lesson01_img_01.png
3824 ms
img_top_02.jpg
3978 ms
ico_q.gif
3994 ms
ico_arw_btn_on.png
4020 ms
btn.js
169 ms
widgets.js
127 ms
collect
28 ms
js
69 ms
init_embed.js
67 ms
ico_marker.png
3874 ms
79 ms
xd_arbiter.php
206 ms
xd_arbiter.php
402 ms
s_menu_01.jpg
4097 ms
common.js
98 ms
map.js
100 ms
google4.png
236 ms
overlay.js
146 ms
util.js
233 ms
onion.js
254 ms
search_impl.js
255 ms
StaticMapService.GetMapImage
546 ms
s_menu_02.jpg
3849 ms
s_menu_03.jpg
5588 ms
stats.js
158 ms
StaticMapService.GetMapImage
407 ms
openhand_8_8.cur
160 ms
ViewportInfoService.GetViewportInfo
155 ms
ViewportInfoService.GetViewportInfo
150 ms
kh
317 ms
kh
340 ms
transparent.png
187 ms
ViewportInfoService.GetViewportInfo
265 ms
ViewportInfoService.GetViewportInfo
182 ms
kh
331 ms
kh
335 ms
s_menu_04.jpg
3788 ms
s_menu_05.jpg
3920 ms
s_menu_06.jpg
3742 ms
controls.js
43 ms
s_menu_08.png
4099 ms
ViewportInfoService.GetViewportInfo
147 ms
vt
213 ms
vt
316 ms
css
218 ms
vt
237 ms
vt
223 ms
vt
227 ms
vt
222 ms
vt
236 ms
entity11.png
152 ms
mapcnt6.png
102 ms
sv5.png
99 ms
ViewportInfoService.GetViewportInfo
79 ms
tmapctrl.png
69 ms
vt
216 ms
vt
201 ms
vt
240 ms
vt
210 ms
vt
219 ms
vt
209 ms
vt
290 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
23 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
27 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
37 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
38 ms
AuthenticationService.Authenticate
24 ms
s_menu_bnr.jpg
4055 ms
AuthenticationService.Authenticate
15 ms
s_ttl_contact.gif
3319 ms
s_img_contact.jpg
3802 ms
s_bg_ttl.gif
3291 ms
s_btn_contact_on.gif
2972 ms
s_btn_contact_off.gif
3098 ms
s_btn_contact.gif
2937 ms
s_bnr_01.jpg
3245 ms
s_bnr_02.jpg
3345 ms
s_bnr_03.jpg
3032 ms
btn_page_top.png
2792 ms
f_bg.jpg
3440 ms
f_bnr_contact.png
2810 ms
f_btn_mail_off.png
2426 ms
f_logo.gif
2380 ms
img_slide_01_box.png
2832 ms
ico_arw_btn01_off.png
2243 ms
ico_arw_l_r.png
2341 ms
ico_arw_r_r.png
2214 ms
img_slide_04_box.png
2479 ms
ico_arw_btn01_on.png
2214 ms
img_slide_02_box.png
2495 ms
img_slide_03_box.png
2936 ms
ico_arw_s_01.png
2277 ms
QuotaService.RecordEvent
13 ms
QuotaService.RecordEvent
14 ms
reina-park.com 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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
reina-park.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
reina-park.com 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reina-park.com 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 Reina-park.com 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.
reina-park.com
Open Graph description is not detected on the main page of Reina Park. 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: