13.4 sec in total
5.4 sec
7.9 sec
114 ms
Welcome to wh.mo homepage info - get ready to check Wh best content right away, or after learning these important things about wh.mo
Visit wh.moWe analyzed Wh.mo page load time and found that the first response time was 5.4 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wh.mo performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value5.2 s
24/100
25%
Value11.1 s
5/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value5.3 s
73/100
10%
5357 ms
505 ms
761 ms
764 ms
779 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that all of those requests were addressed to Wh.mo and no external sources were called. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Wh.mo.
Page size can be reduced by 35.2 kB (78%)
45.2 kB
10.0 kB
In fact, the total size of Wh.mo main page is 45.2 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. Javascripts take 23.5 kB which makes up the majority of the site volume.
Potential reduce by 15.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. This page needs HTML code to be minified as it can gain 4.4 kB, which is 22% 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 15.7 kB or 78% of the original size.
Potential reduce by 18.2 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 18.2 kB or 78% of the original size.
Potential reduce by 1.3 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. Wh.mo needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 78% of the original size.
Number of requests can be reduced by 23 (56%)
41
18
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
wh.mo
5357 ms
mherit.css
505 ms
common.js
761 ms
AC_RunActiveContent.js
764 ms
Common.js
779 ms
bg.gif
754 ms
unesco.gif
254 ms
WHC.gif
254 ms
spacer.gif
258 ms
index04.gif
497 ms
index05.gif
501 ms
index06.gif
504 ms
index07.gif
509 ms
index12C.gif
719 ms
index13.gif
742 ms
index15.gif
749 ms
index16.gif
750 ms
menu06.gif
760 ms
indexC.gif
973 ms
menu10.gif
989 ms
b1C.gif
1004 ms
b2C.gif
1010 ms
b3C.gif
1009 ms
b4C.gif
1014 ms
b5C.gif
1224 ms
menu07.gif
1217 ms
b6C.gif
1027 ms
b7C.gif
1032 ms
menu09.gif
1031 ms
menu12.gif
1041 ms
MHLOGO.gif
1245 ms
mheritlink8C.gif
1511 ms
mheritlink1c.gif
1282 ms
mheritlink9c.gif
1537 ms
mheritlink7C.gif
1285 ms
mheritlink4c.gif
1546 ms
mheritlink6c.gif
1504 ms
webmaster.gif
1533 ms
index04overC.gif
1005 ms
index05overC.gif
1044 ms
index06overC.gif
252 ms
index07overC.gif
1267 ms
index04over.gif
254 ms
index05over.gif
249 ms
index06over.gif
499 ms
index07over.gif
1017 ms
wh.mo accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
Image elements do not have [alt] attributes
Links do not have a discernible name
wh.mo 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
wh.mo SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
JA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wh.mo can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Wh.mo 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.
wh.mo
Open Graph description is not detected on the main page of Wh. 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: