11.2 sec in total
1.4 sec
9.6 sec
198 ms
Click here to check amazing Orh content for Japan. Otherwise, check out these important facts you probably never knew about orh.go.jp
大阪労災病院,労災病院,大阪,大阪府,大阪府堺市,堺市,堺市北区,医療機能評価認定病院,機能評価,がん拠点,地域がん診療連携拠点病院,がん拠点病院,内科,精神科,循環器内科,外科,脳神経外科,皮膚科,形成外科,産婦人科,耳鼻咽喉科,放射線科,歯科口腔外科,精神科,消化器内科,小児科,整形外科,心臓血管外科,泌尿器科,眼科,リハビリテーション科,麻酔科,病理診断科,乳腺外科,消化器外科,救急部,地域...
Visit orh.go.jpWe analyzed Orh.go.jp page load time and found that the first response time was 1.4 sec and then it took 9.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.
orh.go.jp performance score
1378 ms
359 ms
361 ms
1814 ms
392 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 95% of them (73 requests) were addressed to the original Orh.go.jp, 3% (2 requests) were made to Rofuku.go.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Orh.go.jp.
Page size can be reduced by 421.8 kB (42%)
1.0 MB
581.3 kB
In fact, the total size of Orh.go.jp main page is 1.0 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. 20% of websites need less resources to load. Images take 791.4 kB which makes up the majority of the site volume.
Potential reduce by 65.8 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 48.5 kB, which is 66% 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 65.8 kB or 90% of the original size.
Potential reduce by 270.5 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, Orh needs image optimization as it can save up to 270.5 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 60.0 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 60.0 kB or 56% of the original size.
Potential reduce by 25.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. Orh.go.jp needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 80% of the original size.
Number of requests can be reduced by 26 (35%)
74
48
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
orh.go.jp
1378 ms
common.css
359 ms
top.css
361 ms
jquery-1.4.4.min.js
1814 ms
base.js
392 ms
fontsize.js
396 ms
base.css
366 ms
menu.css
382 ms
contents.css
395 ms
sp.css
636 ms
print.css
371 ms
counter.cgi
790 ms
hp_access_log.cgi
618 ms
body_bg.gif
373 ms
header_bg.gif
377 ms
header_btn_sitemap.gif
379 ms
header_btn_toiawase.gif
397 ms
header_btn_access.gif
399 ms
leftmenu_bg.gif
400 ms
mainimage.jpg
2500 ms
logo.png
1161 ms
header_btn_fontsize.gif
755 ms
bnr_google.gif
784 ms
bnr_for_doctor.jpg
949 ms
annai_bg.jpg
782 ms
annai_foot.jpg
1312 ms
annai_btn_01.jpg
1489 ms
listmark01.gif
1311 ms
nyuin_bg.jpg
1341 ms
nyuin_foot.jpg
1533 ms
nyuin_btn_01.jpg
1672 ms
jushin_bg.jpg
1683 ms
jushin_foot.jpg
1731 ms
jushin_btn_01.jpg
1877 ms
recruit_bg.jpg
1890 ms
recruit_foot.jpg
2042 ms
recruit_btn_01.jpg
2053 ms
oshirase_bg.gif
2120 ms
oshirase_foot.gif
2244 ms
h3_bg.gif
2270 ms
oshirase_btn_01.jpg
2585 ms
oshirase_btn_02_1.jpg
2595 ms
oshirase_btn_03.jpg
3966 ms
icon_new.gif
2618 ms
oshirase_koushin.jpg
2650 ms
quicklink_bg.gif
2885 ms
quicklink_foot.gif
2975 ms
quicklink_ttl.gif
2987 ms
hp_access_log.cgi
578 ms
kinen.jpg
3787 ms
ga.js
22 ms
__utm.gif
22 ms
btn_yobomodel.png
3440 ms
btn_ryoritsumodel.png
3973 ms
btn_research12.png
4221 ms
btn_kifu.jpg
2978 ms
btn_shienbyouin.jpg
3352 ms
btn_gankyoten.jpg
3746 ms
btn_gan.jpg
3786 ms
btn_team.jpg
3841 ms
btn_seminar_jujisha.jpg
3954 ms
btn_seminar_shimin.jpg
3922 ms
btn_nurse.jpg
3931 ms
btn_kanwa.png
3616 ms
btn_soamic.jpg
4455 ms
btn_dock.jpg
3872 ms
btn_kinrousha.jpg
3835 ms
btn_kaigai.jpg
3897 ms
btn_shinsai.jpg
3650 ms
icon_hyoka.jpg
4156 ms
btn_yobo.gif
3870 ms
btn_kango.gif
3811 ms
icon_mail.gif
3819 ms
listmark02.gif
3776 ms
copyright.jpg
4139 ms
oshirase_btn_over.gif
380 ms
oshirase_btn_02_2.jpg
589 ms
orh.go.jp SEO score
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orh.go.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Orh.go.jp main page’s claimed encoding is shift_jis. 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.
orh.go.jp
Open Graph description is not detected on the main page of Orh. 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: