15.8 sec in total
1.3 sec
14 sec
401 ms
Welcome to oomoriseiko.info homepage info - get ready to check Oomoriseiko best content for Japan right away, or after learning these important things about oomoriseiko.info
Visit oomoriseiko.infoWe analyzed Oomoriseiko.info page load time and found that the first response time was 1.3 sec and then it took 14.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
oomoriseiko.info performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value49.2 s
0/100
25%
Value16.7 s
0/100
10%
Value3,690 ms
1/100
30%
Value0.412
24/100
15%
Value45.3 s
0/100
10%
1342 ms
388 ms
779 ms
597 ms
603 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 60% of them (93 requests) were addressed to the original Oomoriseiko.info, 13% (20 requests) were made to Pbs.twimg.com and 5% (8 requests) were made to Abs.twimg.com. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Oomoriseiko.info.
Page size can be reduced by 718.8 kB (15%)
4.6 MB
3.9 MB
In fact, the total size of Oomoriseiko.info main page is 4.6 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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 49.1 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 49.1 kB or 81% of the original size.
Potential reduce by 86.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. Oomoriseiko images are well optimized though.
Potential reduce by 308.6 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 308.6 kB or 66% of the original size.
Potential reduce by 274.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. Oomoriseiko.info needs all CSS files to be minified and compressed as it can save up to 274.9 kB or 84% of the original size.
Number of requests can be reduced by 35 (23%)
149
114
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oomoriseiko. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
oomoriseiko.info
1342 ms
base.css
388 ms
style.css
779 ms
jquery.fancybox.css
597 ms
jquery.mCustomScrollbar.css
603 ms
jquery.js
1199 ms
jquery.easing.js
772 ms
customRollOver.js
986 ms
jquery.fancybox.js
1408 ms
jquery.mousewheel.js
1141 ms
jquery.mCustomScrollbar.js
1689 ms
rssFeed.js
1162 ms
facebookFeed.js
1367 ms
script.js
1746 ms
g-a.js
1533 ms
ga.js
28 ms
header_logo.jpg
687 ms
header_top_off.jpg
471 ms
header_news_off.jpg
401 ms
header_live_off.jpg
401 ms
header_schedule_off.jpg
531 ms
header_profile_off.jpg
529 ms
header_discography_off.jpg
785 ms
header_goods_off.jpg
878 ms
header_youtube_off.jpg
883 ms
sns_facebook_off.jpg
930 ms
sns_twitter_off.jpg
952 ms
sns_staff_off.jpg
1106 ms
sns_youtube_off.jpg
1198 ms
sns_livedoor_off.jpg
1294 ms
header_contact_off.jpg
1286 ms
fc.jpg
2306 ms
tour2016.jpg
2524 ms
tour2016_detail_off.jpg
1482 ms
tokyoblackhole.jpg
2872 ms
aishiteru_buy_off.jpg
1742 ms
aishiteru_detail_off.jpg
1687 ms
gnext.jpg
2991 ms
aishiteru.jpg
3435 ms
live_visual.jpg
4116 ms
live_tour_off.jpg
3078 ms
live_other_off.jpg
2940 ms
navi_out.jpg
3273 ms
cover.jpg
3335 ms
whats_title_off.jpg
4217 ms
schedule_title_off.jpg
4028 ms
live_title_off.jpg
4220 ms
profile_title_off.jpg
4330 ms
twitter_title_off.jpg
4607 ms
facebook_title_off.jpg
5187 ms
movie_title_off.jpg
5485 ms
gtm.js
68 ms
blog_title_off.jpg
5154 ms
widgets.js
99 ms
__utm.gif
67 ms
sdk.js
292 ms
analytics.js
52 ms
Dk-mVzTXWPE
132 ms
collect
71 ms
collect
114 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
200 ms
www-embed-player-vfl-z2BtK.css
65 ms
www-embed-player.js
103 ms
base.js
219 ms
goods_title_off.jpg
4786 ms
appli_title_off.jpg
5130 ms
syndication
193 ms
444036078194794496
334 ms
mm_title_off.jpg
5007 ms
footer_privacy_off.jpg
5042 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
71 ms
ad_status.js
66 ms
footer_policy_off.jpg
4918 ms
175 ms
xd_arbiter.php
276 ms
xd_arbiter.php
495 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
97 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
98 ms
footer_copyright.jpg
4897 ms
wrapper_a.jpg
7019 ms
proxy.jpg
142 ms
1f4af.png
129 ms
BHjCGNihAAkQGGWV.jpg
290 ms
9DakBUMDjYNjZ3Ov.jpg
333 ms
2728.png
122 ms
1f468-200d-1f468-200d-1f467-200d-1f466.png
127 ms
1f469-200d-1f469-200d-1f467-200d-1f466.png
127 ms
1f46a.png
125 ms
1f37c.png
126 ms
1f30e.png
128 ms
1f646.png
129 ms
proxy.jpg
206 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
76 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
102 ms
wrapper_b.jpg
5987 ms
wrapper_c.jpg
6634 ms
header_top_on.jpg
5025 ms
ZYqil9l-_normal.jpg
223 ms
elT_-wFB_normal.jpg
230 ms
Mv4fgDci_normal.jpg
222 ms
bqgl3n5i_normal.jpg
232 ms
lBmtyvZM_normal.jpg
233 ms
9Ob0wQmC_normal.jpeg
248 ms
oJDs3vyC_normal.jpg
247 ms
EOB2ZTEx_normal.jpeg
249 ms
l1OyedFn_normal.jpg
254 ms
Xe2m_whR_normal.jpg
431 ms
Cei__0jWwAE7OaM.jpg:small
386 ms
CeeidZ3W8AAZfXO.jpg:small
276 ms
CeZRGfZVAAAfprX.jpg:small
278 ms
Cd_znaZUMAAJEDv.jpg:small
298 ms
CejjqocXEAA7UZh.jpg:small
331 ms
Cejjq_qWIAEWfSd.jpg:small
417 ms
CeZSRNzUkAABgVg.jpg:small
307 ms
CeZSSTXUsAAWA7z.jpg:small
589 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
43 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
52 ms
proxy.jpg
60 ms
jot.html
27 ms
feed
529 ms
header_news_on.jpg
206 ms
header_live_on.jpg
201 ms
header_schedule_on.jpg
378 ms
header_profile_on.jpg
402 ms
header_discography_on.jpg
404 ms
header_goods_on.jpg
405 ms
header_youtube_on.jpg
586 ms
sns_facebook_on.jpg
592 ms
sns_twitter_on.jpg
780 ms
sns_staff_on.jpg
787 ms
sns_youtube_on.jpg
789 ms
sns_livedoor_on.jpg
798 ms
header_contact_on.jpg
956 ms
tour2016_detail_on.jpg
998 ms
aishiteru_buy_on.jpg
1157 ms
aishiteru_detail_on.jpg
1160 ms
live_tour_on.jpg
1172 ms
live_other_on.jpg
1181 ms
whats_title_on.jpg
2373 ms
schedule_title_on.jpg
1957 ms
live_title_on.jpg
2144 ms
profile_title_on.jpg
2183 ms
twitter_title_on.jpg
2759 ms
facebook_title_on.jpg
2586 ms
movie_title_on.jpg
3478 ms
blog_title_on.jpg
3164 ms
goods_title_on.jpg
3182 ms
appli_title_on.jpg
3637 ms
mm_title_on.jpg
3833 ms
footer_privacy_on.jpg
3346 ms
footer_policy_on.jpg
3564 ms
navi_over.jpg
3574 ms
486908_1150073928349535_3458173644288454843_n.jpg
281 ms
1456800_1146025875421007_3224452005603842086_n.jpg
320 ms
12733578_1132758120081116_6857935995913506390_n.jpg
386 ms
oomoriseiko.info 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
oomoriseiko.info 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
oomoriseiko.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Oomoriseiko.info 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 Oomoriseiko.info 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.
oomoriseiko.info
Open Graph description is not detected on the main page of Oomoriseiko. 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: