2 sec in total
413 ms
1.3 sec
265 ms
Welcome to meforum.mn homepage info - get ready to check Meforum best content for Mongolia right away, or after learning these important things about meforum.mn
Mongolia Economic Forum 2024
Visit meforum.mnWe analyzed Meforum.mn page load time and found that the first response time was 413 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
meforum.mn performance score
name
value
score
weighting
Value17.3 s
0/100
10%
Value35.9 s
0/100
25%
Value27.6 s
0/100
10%
Value1,300 ms
18/100
30%
Value0.134
80/100
15%
Value34.6 s
0/100
10%
413 ms
96 ms
71 ms
99 ms
69 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 99% of them (71 requests) were addressed to the original Meforum.mn, 1% (1 request) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (478 ms) belongs to the original domain Meforum.mn.
Page size can be reduced by 432.9 kB (25%)
1.7 MB
1.3 MB
In fact, the total size of Meforum.mn main page is 1.7 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 27.9 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 8.2 kB, which is 25% 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 27.9 kB or 84% of the original size.
Potential reduce by 199.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. Obviously, Meforum needs image optimization as it can save up to 199.0 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 151.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 151.2 kB or 75% of the original size.
Potential reduce by 54.8 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. Meforum.mn needs all CSS files to be minified and compressed as it can save up to 54.8 kB or 82% of the original size.
Number of requests can be reduced by 9 (14%)
66
57
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meforum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
meforum.mn
413 ms
font-awesome.css
96 ms
header.css
71 ms
component.css
99 ms
owl.carousel.css
69 ms
footer.css
69 ms
modernizr.custom.js
71 ms
jquery-2.0.2.min.js
198 ms
jquery.validate.js
165 ms
other.js
106 ms
owl.carousel.js
167 ms
jquery.dlmenu.js
130 ms
0.jpg
84 ms
back11.jpg
136 ms
main_menu_back.png
42 ms
logo.png
39 ms
zar_back.png
60 ms
3f9629f5a56d0bf15a34ffcbb9c36db4.png
46 ms
1cf419b760d0d7e2bffffb837f25a659.jpg
51 ms
smile_logo.png
78 ms
36fb60b3530708d086c55f8f74e57837.jpg
79 ms
4e82bb4df0b3567604c7bfd3b215e14e.png
86 ms
aee5b7c218cdc0a02922eda2de146285.JPG
90 ms
c7fac96e48c19e5e9752f3b42ff75638.jpg
100 ms
0d47f082d90091b2cc75e07912659890.jpg
122 ms
779f46e28270d48f908b9584ea1bebbe.jpg
116 ms
54d5bcaa56ba0862c6272177eb3681cb.jpg
126 ms
6c441d5b189dc626142cca6d391006c5.jpg
136 ms
15403314351ece0aee8fb2325aa1806a.jpg
141 ms
2cf06bcef3a2aeec34a02f659b457384.png
255 ms
8e5f5439c2b9f7e850be063c47503268.jpg
162 ms
58fb55dc76eee4229b56a3a89c5190f1.jpg
177 ms
3d4d83081b81c8e6543954b5fe1a48a1.jpg
173 ms
3457a28f59f9b0315636d9ba3df25be2.jpg
171 ms
49ae62db3e4eebd89c4a2adb6d2c23e2.jpg
185 ms
sponsor_icon.png
203 ms
428926b57138c137fea404c1e03f0be7.jpg
212 ms
2ac0200611beb73065d225eb54f5cdb9.jpg
211 ms
f881679cbda63c0e4138ccfe205bb67a.png
226 ms
113c9beb6de935c5d82c490590316014.jpg
288 ms
1b89bf622116c388c2e3bf17167acdf8.jpg
336 ms
f1aead979dbd31f5dd038d94ba567ccb.jpg
250 ms
a9c025de01b8419707184316fda4ed6b.png
285 ms
226d6fba7f706bc0c354a795748fbf06.jpg
322 ms
8a32ec470acf226efc87c5b005770bb9.png
341 ms
ada554ef2b0a5bee1365866a1a4f0b7c.png
299 ms
cb9cb5e8bbd1460575bfbabd31d38649.png
342 ms
0f068665718a9453d1704209938eea2d.png
331 ms
OpenSans-Regular.ttf
436 ms
fontawesome-webfont.woff
425 ms
OpenSans-Semibold.ttf
431 ms
OpenSans-Light.ttf
470 ms
OpenSans-Bold.ttf
413 ms
177d7175e935b906dab0f37fa00dfc5c.png
329 ms
d1be2cc795bb6c5a24e3635857d5e7c5.png
371 ms
36cb5aa5fc0b26d92b91966adf908646.png
410 ms
21ede757fe5fca4392a1c68b9b57071e.png
400 ms
29df583d56e5544c32eb1ddc3e8d208a.jpg
398 ms
c8ab4cf06b8394c771fab19881b63c46.png
391 ms
6f10f866ab804c9697d0d32329fc0b5a.png
420 ms
923978433f9d381d871d27d3ecd70186.jpg
421 ms
5e9a50d9d2def5151127199c226a07b2.png
478 ms
footer_back.png
405 ms
footer_logo.png
401 ms
android.png
414 ms
iphone.png
416 ms
ipad.png
403 ms
facebook.jpg
404 ms
twitter.jpg
404 ms
youtube.png
410 ms
instagram.jpg
415 ms
email.png
404 ms
meforum.mn accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
meforum.mn 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
Missing source maps for large first-party JavaScript
meforum.mn 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Meforum.mn can be misinterpreted by Google and other search engines. Our service has detected that English 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 Meforum.mn 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.
meforum.mn
Open Graph description is not detected on the main page of Meforum. 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: