Tools & Wizards About Us
meforum.mn screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

meforum.mn

Meforum 2024

Page Load Speed

7.1 sec in total

First Response

742 ms

Resources Loaded

6 sec

Page Rendered

402 ms

meforum.mn screenshot

About Website

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.mn

Key Findings

We analyzed Meforum.mn page load time and found that the first response time was 742 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

meforum.mn performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value26.5 s

0/100

25%

SI (Speed Index)

Value22.7 s

0/100

10%

TBT (Total Blocking Time)

Value4,260 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.158

74/100

15%

TTI (Time to Interactive)

Value25.2 s

0/100

10%

Network Requests Diagram

meforum.mn

742 ms

meforum.mn

1248 ms

css

32 ms

bootstrap.min.css

483 ms

all.min.css

914 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 67% of them (57 requests) were addressed to the original Meforum.mn, 9% (8 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Meforum.mn.

Page Optimization Overview & Recommendations

Page size can be reduced by 363.2 kB (12%)

Content Size

3.1 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Meforum.mn main page is 3.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 143.8 kB

  • Original 166.6 kB
  • After minification 144.3 kB
  • After compression 22.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 22.3 kB, which is 13% 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 143.8 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 155.3 kB

  • Original 2.2 MB
  • After minification 2.0 MB

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. Meforum images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 49.9 kB

  • Original 565.0 kB
  • After minification 564.7 kB
  • After compression 515.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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 14.2 kB

  • Original 235.6 kB
  • After minification 235.6 kB
  • After compression 221.4 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 49 (70%)

Requests Now

70

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 70 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 31 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

meforum.mn

meforum.mn

742 ms

meforum.mn

meforum.mn

1248 ms

css

css

32 ms

bootstrap.min.css

bootstrap.min.css

483 ms

all.min.css

all.min.css

914 ms

animate.compat.css

animate.compat.css

697 ms

simple-line-icons.min.css

simple-line-icons.min.css

707 ms

owl.carousel.min.css

owl.carousel.min.css

708 ms

owl.theme.default.min.css

owl.theme.default.min.css

723 ms

magnific-popup.min.css

magnific-popup.min.css

749 ms

theme.css

theme.css

1160 ms

theme-elements.css

theme-elements.css

1412 ms

theme-blog.css

theme-blog.css

942 ms

theme-shop.css

theme-shop.css

964 ms

settings.css

settings.css

1001 ms

layers.css

layers.css

1143 ms

navigation.css

navigation.css

1178 ms

demo-event.css

demo-event.css

1204 ms

skin-event1.css

skin-event1.css

1254 ms

custom.css

custom.css

1371 ms

modernizr.min.js

modernizr.min.js

1391 ms

intlTelInput.css

intlTelInput.css

70 ms

intlTelInput.min.js

intlTelInput.min.js

84 ms

intlTelInput.css

intlTelInput.css

28 ms

intlTelInput.min.js

intlTelInput.min.js

15 ms

jquery.min.js

jquery.min.js

1464 ms

jquery.appear.min.js

jquery.appear.min.js

1302 ms

jquery.easing.min.js

jquery.easing.min.js

1304 ms

jquery.cookie.min.js

jquery.cookie.min.js

1404 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

1405 ms

jquery.validate.min.js

jquery.validate.min.js

1431 ms

jquery.easypiechart.min.js

jquery.easypiechart.min.js

1499 ms

jquery.gmap.min.js

jquery.gmap.min.js

1625 ms

lazysizes.min.js

lazysizes.min.js

1822 ms

jquery.isotope.min.js

jquery.isotope.min.js

1979 ms

owl.carousel.min.js

owl.carousel.min.js

2001 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

2000 ms

jquery.vide.min.js

jquery.vide.min.js

2005 ms

vivus.min.js

vivus.min.js

2005 ms

theme.js

theme.js

2335 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

2186 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

2473 ms

js

js

71 ms

view.contact.js

view.contact.js

2334 ms

demo-event.js

demo-event.js

2085 ms

theme.init.js

theme.init.js

1918 ms

gtm.js

gtm.js

144 ms

-abbVknuz4E

-abbVknuz4E

184 ms

logo02.svg

logo02.svg

1232 ms

mn.png

mn.png

1230 ms

bg2023_1.jpg

bg2023_1.jpg

2753 ms

event.jpg

event.jpg

1383 ms

about-icon.png

about-icon.png

1382 ms

col1.png

col1.png

1464 ms

turiinordon.jpeg

turiinordon.jpeg

2641 ms

chingis.jpg

chingis.jpg

1960 ms

tsengeldeh.jpg

tsengeldeh.jpg

2455 ms

android-download.png

android-download.png

1589 ms

apple-download.png

apple-download.png

1699 ms

appqr.png

appqr.png

1821 ms

logo01.svg

logo01.svg

1942 ms

inst_1.png

inst_1.png

2052 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

23 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

29 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

51 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

59 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

60 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

59 ms

fa-solid-900.woff

fa-solid-900.woff

2351 ms

fa-regular-400.woff

fa-regular-400.woff

2139 ms

fa-brands-400.woff

fa-brands-400.woff

2455 ms

www-player.css

www-player.css

26 ms

www-embed-player.js

www-embed-player.js

94 ms

base.js

base.js

219 ms

js

js

124 ms

fbevents.js

fbevents.js

197 ms

ad_status.js

ad_status.js

234 ms

-IE9NVOjDHeKbguIKoMv97ZGvbdnRzECCJkBZGu5IKs.js

-IE9NVOjDHeKbguIKoMv97ZGvbdnRzECCJkBZGu5IKs.js

153 ms

embed.js

embed.js

52 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

42 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

41 ms

id

id

16 ms

Create

Create

113 ms

GenerateIT

GenerateIT

18 ms

flags.png

flags.png

26 ms

Accessibility Review

meforum.mn accessibility score

69

Accessibility Issues

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

meforum.mn best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

meforum.mn SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

meforum.mn

Open Graph data is detected on the main page of Meforum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: