15 sec in total
515 ms
14.1 sec
418 ms
Visit kobekyo.com now to see the best up-to-date Kobekyo content for Japan and also check out these interesting facts you probably never knew about kobekyo.com
全国No.1の個別指導塾、個別教室のトライのトップページです。
Visit kobekyo.comWe analyzed Kobekyo.com page load time and found that the first response time was 515 ms and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kobekyo.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value6.3 s
10/100
25%
Value9.5 s
12/100
10%
Value1,990 ms
8/100
30%
Value0
100/100
15%
Value21.1 s
1/100
10%
515 ms
1324 ms
760 ms
646 ms
969 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 73% of them (113 requests) were addressed to the original Kobekyo.com, 6% (10 requests) were made to Tg.socdm.com and 3% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Kobekyo.com.
Page size can be reduced by 862.1 kB (26%)
3.3 MB
2.5 MB
In fact, the total size of Kobekyo.com main page is 3.3 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. 35% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 33.0 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 33.0 kB or 75% of the original size.
Potential reduce by 511.7 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, Kobekyo needs image optimization as it can save up to 511.7 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 139.8 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 139.8 kB or 56% of the original size.
Potential reduce by 177.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. Kobekyo.com needs all CSS files to be minified and compressed as it can save up to 177.6 kB or 88% of the original size.
Number of requests can be reduced by 37 (27%)
139
102
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kobekyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
kobekyo.com
515 ms
www.kobekyo.com
1324 ms
base.css
760 ms
top_new2016.css
646 ms
jquery.mCustomScrollbar.min.css
969 ms
rollover.js
334 ms
jquery.min.js
31 ms
jquery.easing.min.js
690 ms
jquery.bxslider.min.js
1140 ms
top_new2016.js
807 ms
jquery.remodal.js
1125 ms
jquery.mCustomScrollbar.min.js
1448 ms
jquery.mousewheel-3.0.6.min.js
1063 ms
swfobject.js
1296 ms
cvtag.js
1294 ms
footer.php
1259 ms
conversion.js
19 ms
clear.css
702 ms
style01.css
1804 ms
jquery.mousewheel.min.js
104 ms
logo.gif
165 ms
gnaiv_tel.png
325 ms
gnavi_bt_taiken.png
326 ms
gnavi_bt_inq.png
509 ms
gnavi_bg_001.gif
355 ms
gnavi_bt_rinen.gif
355 ms
gnavi_bt_school.gif
501 ms
gnavi_bt_course.gif
670 ms
gnavi_bt_riyu.gif
680 ms
gnavi_bt_qa.gif
681 ms
pc_main.jpg
1660 ms
kv_tryit.jpg
2502 ms
kv_002.jpg
1676 ms
kv_003.jpg
1786 ms
kv_005.jpg
2125 ms
arw_left.png
1042 ms
thumb_inds.png
1368 ms
arw_right.png
1677 ms
keyvisual-catch_img.png
2010 ms
bg_inquest_top.png
2010 ms
bg_inquest_title.png
2154 ms
ic_inquest_box.png
2107 ms
bnr_campaign_inquest.jpg
2739 ms
bnr_area_inquest.jpg
2638 ms
btn_course_sh_inquest.png
2639 ms
btn_course_jh_inquest.png
2605 ms
btn_course_hs_inquest.png
2685 ms
txt_inquest.png
3006 ms
entry-btn_taiken.png
2960 ms
entry_btn_inq.png
3091 ms
entry_tel_img.png
2958 ms
try-point1_img.png
3321 ms
try-todetails_btn.png
3086 ms
try-point2_img.png
3614 ms
try-point3_img.png
3624 ms
bnr_campaign.jpg
3596 ms
analytics.js
22 ms
s_retargeting.js
551 ms
linkid.js
10 ms
collect
11 ms
collect
62 ms
bnr_tryit.jpg
3574 ms
bnr_pro_big.jpg
3577 ms
recomend_item1_img.png
4244 ms
recomend_item2_img.png
4399 ms
recomend_item3_img.png
4549 ms
bg_area_list.png
3492 ms
news_bg_head.png
3585 ms
50 ms
64 ms
61 ms
target.js
26 ms
news_bg_foot.png
3560 ms
news_h.png
3631 ms
program_h.png
3749 ms
blade_track_jp.js
346 ms
so.js
671 ms
45 ms
35 ms
24 ms
24 ms
23 ms
cookie_enabled_get.html
336 ms
bnr_img_modal.png
5306 ms
js
198 ms
btn_campaign_modal.png
3423 ms
bl_track.cgi
335 ms
v3
190 ms
js
415 ms
btn_entry_modal.png
3280 ms
btn_close_modal.png
3226 ms
ftr_ref_bnr_try.gif
3408 ms
ftr_ref_bnr_kobetsu.gif
3361 ms
sosync
235 ms
beacon.html
20 ms
ftr_ref_bnr_trygakuin.gif
3209 ms
ftr_ref_bnr_adult.gif
3207 ms
ftr_ref_bnr_tryit.gif
3159 ms
ftr_ref_bnr_med.gif
3283 ms
ftr_ref_bnr_integra.gif
3312 ms
18 ms
sync
608 ms
sync_before
191 ms
sync_before
192 ms
sync_before
343 ms
idsync
385 ms
sync
373 ms
20 ms
pixel
20 ms
cs
298 ms
sync
518 ms
ftr_ref_bnr_tryplus.gif
3060 ms
sync
601 ms
Pug
17 ms
is
736 ms
ftr_ref_bnr_sports.gif
2969 ms
sd
30 ms
ftr_ref_bnr_mygm.gif
2982 ms
foot_bg_002.gif
3090 ms
foot_bg_001.gif
3261 ms
thumb_inds_on.png
3144 ms
tap.php
544 ms
gnavi_bt_taiken_on.png
889 ms
gnavi_bt_inq_on.png
928 ms
gnavi_bt_rinen_on.gif
324 ms
gnavi_bt_school_on.gif
324 ms
gnavi_bt_course_on.gif
329 ms
gnavi_bt_riyu_on.gif
337 ms
gnavi_bt_qa_on.gif
646 ms
kv_005_on.jpg
1686 ms
pc_main_on.jpg
1905 ms
kv_tryit_on.jpg
2282 ms
kv_002_on.jpg
1816 ms
kv_003_on.jpg
1846 ms
arw_left_on.png
1265 ms
arw_right_on.png
1620 ms
bnr_campaign_inquest_on.jpg
2263 ms
bnr_area_inquest_on.jpg
2531 ms
entry-btn_taiken_on.png
2828 ms
entry_btn_inq_on.png
2812 ms
try-todetails_btn_on.png
2212 ms
bnr_pro_big_on.jpg
2886 ms
ftr_ref_bnr_try_on.gif
2596 ms
ftr_ref_bnr_kobetsu_on.gif
2601 ms
ftr_ref_bnr_trygakuin_on.gif
2838 ms
ftr_ref_bnr_adult_on.gif
2914 ms
ftr_ref_bnr_tryit_on.gif
2926 ms
ftr_ref_bnr_med_on.gif
3146 ms
ftr_ref_bnr_integra_on.gif
3142 ms
ftr_ref_bnr_tryplus_on.gif
3184 ms
ftr_ref_bnr_sports_on.gif
3244 ms
ftr_ref_bnr_mygm_on.gif
3234 ms
btn_campaign_modal_on.png
3406 ms
btn_entry_modal_on.png
3624 ms
btn_close_modal_on.png
3480 ms
kobekyo.com 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
Links do not have a discernible name
kobekyo.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
kobekyo.com 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 Kobekyo.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 Kobekyo.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.
kobekyo.com
Open Graph description is not detected on the main page of Kobekyo. 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: