6.5 sec in total
261 ms
5.8 sec
385 ms
Visit oiml.org now to see the best up-to-date Oiml content for Malaysia and also check out these interesting facts you probably never knew about oiml.org
OIML: The intergovernmental treaty organization established in 1955 which promotes the global harmonization of legal metrology procedures.
Visit oiml.orgWe analyzed Oiml.org page load time and found that the first response time was 261 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
oiml.org performance score
261 ms
1457 ms
582 ms
250 ms
291 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that all of those requests were addressed to Oiml.org and no external sources were called. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Oiml.org.
Page size can be reduced by 116.3 kB (13%)
893.3 kB
777.0 kB
In fact, the total size of Oiml.org main page is 893.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 837.1 kB which makes up the majority of the site volume.
Potential reduce by 40.5 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 7.8 kB, which is 16% 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 40.5 kB or 83% of the original size.
Potential reduce by 70.0 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. Oiml images are well optimized though.
Potential reduce by 5.9 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 5.9 kB or 77% of the original size.
Number of requests can be reduced by 15 (37%)
41
26
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oiml. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
oiml.org
261 ms
en
1457 ms
base-cachekey-91423e05b25020b68325ee41e7463fda.css
582 ms
resourceplone.app.jquerytools.dateinput-cachekey-f3f80f1d3ae2f1d27951cf1804d966fc.css
250 ms
resourceContentWellPortlets.stylesContentWellPortlets-cachekey-c2af42603ed1913e42c40ebb54b6de87.css
291 ms
resourceProducts.Doormat.stylesheetsdoormat-cachekey-da3e8118513bc0ee0785aac7981836c2.css
298 ms
resourceeasySlider-cachekey-856040cb756ff401a49edca058d0a753.css
341 ms
resourceeasyslider-portlet-cachekey-405015e5c39d5be05521303bc2e602dc.css
437 ms
main.css
617 ms
ploneCustom-cachekey-3d5fa4dea91e7a3e19eef801b7cbf2b6.css
477 ms
at-cachekey-c20e4845a858356ed33dc8dfe01295dc.kss
609 ms
resourceplone.app.jquery-cachekey-7a6216f3bd0b43216e7fbfb5b6dd1887.js
1500 ms
resourcedropdown-menu-cachekey-d3824fea12ad4c022857f7d9f54250ac.js
755 ms
resourceoiml.membersscriptsoimlmembers-cachekey-eb98b3bc4a906cc3a6a77f58a98ca786.js
766 ms
resourceslc.linguatools.staticlinguatools-cachekey-ab090716b182ab8235f9ff89b6b6c373.js
861 ms
resourceeasySlider-cachekey-f78b2a82165f8b000b84d80499f3785c.js
1044 ms
resourceeasyslider-portlet-cachekey-fcb0157027ac1e76919c15178db86ade.js
809 ms
oiml.js
896 ms
awstats-misc-tracker.js
800 ms
background.png
241 ms
search_field.png
222 ms
logo.png
289 ms
safety-en.jpg
608 ms
trade-en.jpg
769 ms
health-en.jpg
644 ms
environment-en.jpg
724 ms
image_categoryportlet
419 ms
image_categoryportlet
481 ms
image_categoryportlet
635 ms
image_categoryportlet
672 ms
image_categoryportlet
815 ms
image_categoryportlet
838 ms
2016-01.jpg
1004 ms
worldmap_sm.png
890 ms
icon-r79.jpg
1225 ms
icon-r144-french.jpg
1201 ms
icon-r145.jpg
1335 ms
icon-r139-3.jpg
1206 ms
poster_thumbnail_2016_EN.jpg
1360 ms
thumbnail-wk.jpg
1531 ms
events_strasbourg.jpg
1996 ms
spinner.gif
1411 ms
arrowdown.png
1388 ms
questrial-regular-webfont.woff
1654 ms
awstats_misc_tracker.js
2389 ms
oiml.org SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oiml.org 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 Oiml.org 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.
oiml.org
Open Graph description is not detected on the main page of Oiml. 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: