16.8 sec in total
539 ms
15.5 sec
773 ms
Click here to check amazing Ondine content for Japan. Otherwise, check out these important facts you probably never knew about ondine.jp
振袖レンタル・販売ならオンディーヌ。人気柄や流行色の振袖コレクションを日本全国展開。一生に一度の成人式、前撮り写真から当日着付まで完全サポート。振袖レンタルはセットで安心の『Ondine』。
Visit ondine.jpWe analyzed Ondine.jp page load time and found that the first response time was 539 ms and then it took 16.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ondine.jp performance score
name
value
score
weighting
Value9.8 s
0/100
10%
Value29.7 s
0/100
25%
Value22.6 s
0/100
10%
Value2,740 ms
3/100
30%
Value0
100/100
15%
Value28.4 s
0/100
10%
539 ms
803 ms
307 ms
320 ms
327 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 94% of them (97 requests) were addressed to the original Ondine.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Ondine.jp.
Page size can be reduced by 357.4 kB (3%)
11.4 MB
11.0 MB
In fact, the total size of Ondine.jp main page is 11.4 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. 55% of websites need less resources to load. Images take 11.0 MB which makes up the majority of the site volume.
Potential reduce by 21.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 21.5 kB or 79% of the original size.
Potential reduce by 104.2 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. Ondine images are well optimized though.
Potential reduce by 176.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 176.2 kB or 71% of the original size.
Potential reduce by 55.6 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. Ondine.jp needs all CSS files to be minified and compressed as it can save up to 55.6 kB or 84% of the original size.
Number of requests can be reduced by 24 (25%)
96
72
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ondine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
ondine.jp
539 ms
www.ondine.jp
803 ms
import.css
307 ms
uniq.css
320 ms
fontsize.css
327 ms
import.js
350 ms
ticker.js
357 ms
jquery.bxslider.js
778 ms
jquery.bxslider.css
606 ms
css
24 ms
normalize.css
337 ms
base.css
344 ms
component.css
366 ms
default.js
180 ms
innerlink.js
335 ms
jquery.js
835 ms
jquery.autoHeight.js
336 ms
jquery.opacity-rollover.js
338 ms
jquery.faderollover.js
1653 ms
jquery_scrolltop.js
522 ms
jquery.easing-1.3.pack.js
637 ms
jquery.fancybox-1.3.4.pack.js
819 ms
jquery.fancybox-1.3.4.css
671 ms
jquery.accordion.js
855 ms
jquery.parts.js
940 ms
viewport.js
994 ms
sp.css
523 ms
analytics.js
116 ms
btn_header02.gif
199 ms
btn_header01.gif
308 ms
img_logo.gif
325 ms
btn_spHeader01.jpg
326 ms
btn_spHeader02.gif
337 ms
mv00.jpg
2063 ms
mv02.jpg
1926 ms
mv03.jpg
1986 ms
mv04.jpg
2878 ms
mv06.jpg
2378 ms
mv_sp00.jpg
1961 ms
mv_sp02.jpg
3221 ms
mv_sp03.jpg
3388 ms
mv_sp04.jpg
3726 ms
mv_sp06.jpg
3702 ms
bg_news.gif
2709 ms
bg_notice.jpg
3908 ms
btn_201603_fair.jpg
3709 ms
btn_festa.jpg
4138 ms
btn_contents01.jpg
4237 ms
btn_photo.jpg
4525 ms
img_rnk04.jpg
4489 ms
bg_rnk01.jpg
4592 ms
img_rnk01.jpg
4738 ms
bg_rnk02.jpg
5154 ms
img_rnk02.jpg
5079 ms
bg_rnk03.jpg
5355 ms
img_rnk03.jpg
5279 ms
bg_rnk04.jpg
5350 ms
bg_rnk05.jpg
5598 ms
img_rnk05.jpg
5910 ms
bg_rnk06.jpg
5962 ms
img_rnk06.jpg
6201 ms
bg_rnk07.jpg
6135 ms
img_rnk07.jpg
6204 ms
bg_rnk08.jpg
6244 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
9 ms
collect
14 ms
collect
64 ms
ga-audiences
40 ms
img_rnk08.jpg
6475 ms
bg_search.gif
6021 ms
btn_search01.png
6831 ms
btn_search02.png
6737 ms
btn_search03.png
6767 ms
btn_search04.png
5320 ms
bg_hakama02.jpg
5219 ms
bg_hakama03.jpg
5822 ms
bg_hakama01.gif
5490 ms
btn_hakama01.jpg
5755 ms
btn_hakama02.jpg
5479 ms
btn_bnrBox01.png
4968 ms
btn_bnrBox02.png
4855 ms
btn_bnrBox04.png
4713 ms
btn_bnrBox05.png
4638 ms
btn_bnrBox03.jpg
5114 ms
bg_plan.gif
4682 ms
btn_plan01.jpg
4908 ms
btn_plan02.jpg
4807 ms
btn_plan03.jpg
4491 ms
btn_plan04.jpg
4360 ms
bg_map.jpg
5087 ms
img_map.png
5136 ms
img_arrow.png
4402 ms
img_logoFooter.png
4071 ms
btn_pc01.jpg
4007 ms
btn_pc02.gif
3990 ms
btn_pc03.gif
4124 ms
scrollup.png
4121 ms
bx_loader.gif
5319 ms
btn_prev.png
3693 ms
btn_next.png
3832 ms
mv_sp00.jpg
4936 ms
img_rnk04.jpg
4250 ms
print.css
345 ms
ondine.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
ondine.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ondine.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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ondine.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 Ondine.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.
ondine.jp
Open Graph data is detected on the main page of Ondine. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: