5.3 sec in total
914 ms
4 sec
348 ms
Click here to check amazing Ohr content for Bosnia and Herzegovina. Otherwise, check out these important facts you probably never knew about ohr.int
Office of the High Representative
Visit ohr.intWe analyzed Ohr.int page load time and found that the first response time was 914 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ohr.int performance score
914 ms
328 ms
132 ms
249 ms
247 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 75% of them (43 requests) were addressed to the original Ohr.int, 5% (3 requests) were made to Staticxx.facebook.com and 4% (2 requests) were made to Listjs.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ohr.int.
Page size can be reduced by 481.0 kB (34%)
1.4 MB
923.5 kB
In fact, the total size of Ohr.int main page is 1.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. 50% of websites need less resources to load. Images take 817.6 kB which makes up the majority of the site volume.
Potential reduce by 52.7 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 52.7 kB or 81% of the original size.
Potential reduce by 49.4 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. Ohr images are well optimized though.
Potential reduce by 191.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 191.8 kB or 71% of the original size.
Potential reduce by 187.0 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. Ohr.int needs all CSS files to be minified and compressed as it can save up to 187.0 kB or 74% of the original size.
Number of requests can be reduced by 29 (56%)
52
23
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ohr. 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 16 to 1 for CSS and as a result speed up the page load time.
www.ohr.int
914 ms
list.js
328 ms
jquery.bxslider.css
132 ms
advanced-responsive-video-embedder-public.css
249 ms
style.css
247 ms
jquery.tosrus.all.min.css
249 ms
admin-ajax.php
1358 ms
dashicons.min.css
381 ms
style.css
263 ms
css
24 ms
bootstrap.min.css
496 ms
custom.css
371 ms
custom-responsive.css
370 ms
font-awesome.min.css
394 ms
responsive-table.css
496 ms
wp-paginate.css
497 ms
jquery.min.js
643 ms
jquery.bxslider.js
532 ms
jquery.tosrus.min.all.js
624 ms
front.js
628 ms
bootstrap.min.js
626 ms
jquery.csbuttons.js
662 ms
slim-081711.css
11 ms
wpBannerizeStyleDefault.css
750 ms
navigation.js
752 ms
skip-link-focus-fix.js
750 ms
hoverIntent.min.js
766 ms
maxmegamenu.js
787 ms
wpBannerizeFrontend.min.js
875 ms
list.js
212 ms
wp-emoji-release.min.js
329 ms
valentin-inzko.jpg
883 ms
header.jpg
771 ms
header-1.png
258 ms
header-2.png
266 ms
header-3.png
381 ms
header-4.png
497 ms
header-5.png
632 ms
logo-phone.png
394 ms
OHRPR-09032016-01-635x316.jpg
589 ms
1Q5A0889-226x140.jpg
517 ms
final02-226x140.jpg
527 ms
OHRPR-22022016-01-226x140.jpg
631 ms
final01-226x140.jpg
646 ms
logo-no-phone.png
653 ms
all.js
270 ms
glyphicons-halflings-regular.woff
715 ms
6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==
36 ms
fontawesome-webfont.woff
892 ms
analytics.js
35 ms
collect
11 ms
collect
63 ms
ga-audiences
36 ms
92 ms
xd_arbiter.php
223 ms
xd_arbiter.php
431 ms
xd_arbiter.php
137 ms
ohr.int SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ohr.int can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ohr.int 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.
ohr.int
Open Graph data is detected on the main page of Ohr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: