10.1 sec in total
1.3 sec
8.3 sec
433 ms
Click here to check amazing Omiaibus content. Otherwise, check out these important facts you probably never knew about omiaibus.com
婚活・お見合いバス.comは季節感溢れる素敵な婚活バスツアーを提供!エクシオジャパンが主催するバス婚で新しい出会いを探してみませんか?
Visit omiaibus.comWe analyzed Omiaibus.com page load time and found that the first response time was 1.3 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
omiaibus.com performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value2.4 s
91/100
25%
Value2.7 s
96/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.2 s
100/100
10%
1328 ms
331 ms
53 ms
334 ms
342 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 67% of them (87 requests) were addressed to the original Omiaibus.com, 11% (14 requests) were made to Static.xx.fbcdn.net and 5% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Omiaibus.com.
Page size can be reduced by 918.0 kB (53%)
1.7 MB
827.9 kB
In fact, the total size of Omiaibus.com main page is 1.7 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 49.4 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. This page needs HTML code to be minified as it can gain 11.8 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 49.4 kB or 80% of the original size.
Potential reduce by 440.3 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. Obviously, Omiaibus needs image optimization as it can save up to 440.3 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 192.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 192.6 kB or 66% of the original size.
Potential reduce by 235.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. Omiaibus.com needs all CSS files to be minified and compressed as it can save up to 235.7 kB or 83% of the original size.
Number of requests can be reduced by 50 (40%)
126
76
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Omiaibus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
omiaibus.com
1328 ms
import.css
331 ms
jsapi
53 ms
rollover.js
334 ms
style.css
342 ms
jQselectable.js
362 ms
jQselectable_init.js
369 ms
top_fade.js
645 ms
jquery.cookie.js
641 ms
timer.js
677 ms
default.css
353 ms
module.css
360 ms
style.css
553 ms
template.css
537 ms
print.css
646 ms
all-site-banner.js
1547 ms
jquery.min.js
72 ms
base.css
189 ms
logo.gif
472 ms
gnavi_top.png
469 ms
gnavi_about.png
471 ms
gnavi_flow.png
468 ms
gnavi_sanka.png
470 ms
gnavi_sch.png
469 ms
gnavi_exp.png
759 ms
gnavi_faq.png
775 ms
top_main_01.jpg
1834 ms
top_main_02.jpg
1803 ms
top_main_03.jpg
1848 ms
1454321047_1
1254 ms
1453883730_1
1411 ms
1454320796_1
1652 ms
1453883388_1
1981 ms
top_cont01.png
1773 ms
banner-no1.png
2045 ms
bnr_smartphone.png
2314 ms
side_thmb01.png
2110 ms
side_thmb02.png
2136 ms
side_thmb03.png
2201 ms
side_thmb04.png
2327 ms
side_thmb05.png
2351 ms
side_thmb06.png
2440 ms
side_thmb07.png
2437 ms
side_thmb08.png
2528 ms
side_thmb09.png
2650 ms
side_thmb10.png
2651 ms
side_thmb11.png
2676 ms
bnr_blognew.png
2759 ms
bnr_spot.png
2780 ms
bnr_jijyo.png
2855 ms
bnr_gourmet.png
3160 ms
bnr_pp.png
3008 ms
totop.png
3374 ms
all.js
127 ms
header_navi.png
3099 ms
W5HYCQ3ZpvA
149 ms
DME5MpsqZP4
174 ms
I167vzBzEMs
172 ms
82 ms
xd_arbiter.php
97 ms
xd_arbiter.php
291 ms
www-embed-player-vflfNyN_r.css
65 ms
www-embed-player.js
92 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
60 ms
ad_status.js
119 ms
body_bg_2.png
2647 ms
top_info_head.png
2735 ms
side_arr.gif
2872 ms
top_info_mid.png
2971 ms
top_info_btm.png
2976 ms
top_sch_head.png
3029 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
158 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
158 ms
top_sch_mid.png
2765 ms
top_sch_from.png
2884 ms
gtm.js
111 ms
analytics.js
18 ms
collect
13 ms
page.php
156 ms
collect
65 ms
top_sch_day.png
2492 ms
WeNUksYuaPI.css
84 ms
UIgJDuvLZnw.css
105 ms
1kPfZUdGrka.js
161 ms
AeiIQ53iqZ6.js
188 ms
Qd7TTBR3F_S.js
187 ms
1dEEvSwLtg5.js
146 ms
b1o_4KKMvfn.js
213 ms
top_sch_btm.png
2344 ms
1390495_740916792588987_293146232_n.png
219 ms
1476094_740917772588889_952490134_n.png
217 ms
10516670_1285782681435726_9126600890265328556_n.jpg
211 ms
12802939_1280815145265813_4935843148453908889_n.jpg
214 ms
12744318_1275138359166825_8541554713159172879_n.jpg
193 ms
12744124_1270399429640718_3695947931697182451_n.jpg
225 ms
12729085_1264563306890997_1360731674275961336_n.jpg
218 ms
wL6VQj7Ab77.png
98 ms
s7jcwEQH7Sx.png
99 ms
GtIpNnEyqq_.png
99 ms
top_cont_formen.png
2138 ms
top_cont_forwomen.png
2078 ms
R9GKCzjAnbk.js
19 ms
AWWjhOengNF.js
21 ms
YnSasnyq68i.js
19 ms
kQf_jlUv-kX.js
21 ms
r_side_spot.png
3033 ms
r_side_jijyo.png
2653 ms
map.png
2205 ms
res_btn.png
2119 ms
side_head.png
2089 ms
side_mid.png
2079 ms
side_btm.png
2246 ms
footer_bg.png
2777 ms
footer.png
2136 ms
logo_on.gif
2405 ms
gnavi_top_on.png
2376 ms
gnavi_about_on.png
2352 ms
gnavi_flow_on.png
2410 ms
gnavi_sanka_on.png
2506 ms
gnavi_sch_on.png
2404 ms
gnavi_exp_on.png
2465 ms
gnavi_faq_on.png
2484 ms
banner-no1_on.png
2613 ms
bnr_blognew_on.png
2552 ms
bnr_spot_on.png
3432 ms
bnr_jijyo_on.png
3121 ms
bnr_gourmet_on.png
2503 ms
totop_on.png
2819 ms
select_right.gif
2521 ms
select_left.gif
2505 ms
omiaibus.com accessibility score
omiaibus.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
omiaibus.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omiaibus.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 Omiaibus.com main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
omiaibus.com
Open Graph description is not detected on the main page of Omiaibus. 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: