Tools & Wizards About Us
m.2gis.ae screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

m.2gis.ae

Map of cities of the UAE — 2GIS

Page Load Speed

3 sec in total

First Response

366 ms

Resources Loaded

2.5 sec

Page Rendered

98 ms

m.2gis.ae screenshot

About Website

Visit m.2gis.ae now to see the best up-to-date M 2GIS content for United Arab Emirates and also check out these interesting facts you probably never knew about m.2gis.ae

A detailed map of cities of the UAE: search by address, phone numbers, photos, opening hours and a convenient route search

Visit m.2gis.ae

Key Findings

We analyzed M.2gis.ae page load time and found that the first response time was 366 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

m.2gis.ae performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

68/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value3,060 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

m.2gis.ae

366 ms

m.2gis.ae

530 ms

2gis.ae

643 ms

museum

220 ms

icon200.png

738 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 22% of them (2 requests) were addressed to the original M.2gis.ae, 56% (5 requests) were made to D-assets.2gis.ru and 22% (2 requests) were made to 2gis.ae. The less responsive or slowest element that took the longest time to load (769 ms) relates to the external source D-assets.2gis.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.5 kB (33%)

Content Size

31.4 kB

After Optimization

20.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of M.2gis.ae main page is 31.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 19.7 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 7.3 kB

  • Original 11.2 kB
  • After minification 11.2 kB
  • After compression 3.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. 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 7.3 kB or 65% of the original size.

Image Optimization

-16%

Potential reduce by 3.1 kB

  • Original 19.7 kB
  • After minification 16.5 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, M 2GIS needs image optimization as it can save up to 3.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 71 B

  • Original 559 B
  • After minification 559 B
  • After compression 488 B

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 71 B or 13% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M 2GIS. According to our analytics all requests are already optimized.

Network Requests Diagram

m.2gis.ae

m.2gis.ae

366 ms

m.2gis.ae

m.2gis.ae

530 ms

2gis.ae

2gis.ae

643 ms

museum

museum

220 ms

icon200.png

icon200.png

738 ms

google-chrome.png

google-chrome.png

744 ms

mozilla-firefox.png

mozilla-firefox.png

753 ms

opera.png

opera.png

747 ms

museum.js

museum.js

769 ms

Accessibility Review

m.2gis.ae accessibility score

54

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

m.2gis.ae best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

m.2gis.ae SEO score

78

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

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

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 M.2gis.ae 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 M.2gis.ae 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

m.2gis.ae

Open Graph description is not detected on the main page of M 2GIS. 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: