2m.ma - SEO Checker - Website Review

Your Website Score is

Similar Ranking

HINDI NEWS INDIA | LIVE NEWS HINDI WEBSITE | STATES - CITIES - POLITICS AND MOVIES NEWS IN हिंदी

webdunia.com

HOME - LOVIN MALTA

lovinmalta.com

VCCS

vccs.edu

DROPSHIPPING SUPPLIERS FOR BEST US/EU PRODUCTS | SPOCKET

spocket.co

PIRATEBAY PROXY LIST - ☠ WORKING PIRATE BAY PROXY SITES AND MIRRORS ☠

piratebay-proxylist.se

ЧИТАТЬ МАНГУ НА РУССКОМ ОНЛАЙН. СВЕЖИЕ ПЕРЕВОДЫ. READ MANGA ONLINE! - READMANGA.ME

readmanga.me

VAGAS EMPREGO | JOBARTIS EMPREGO | EMPREGO EM ANGOLA

jobartis.com

Latest Sites

INVITATION TO REGISTER

home.takepocket.com

GOLIKE

tiktok.golike.one

ACUITY FUNDING

acuityfunding.com

sharenow126.com

MASUK

gm066.com

恭喜，站点创建成功！

51278.cc

m.fun8899jk.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

43 2m.ma Last Updated: 1 year

Success 70% of passed verification steps

Warning 15% of total warning

Errors 15% of total errors, require fast action

Mobile

Performance Desktop Score 48%

Best Practices Desktop Score 46%

SEO Desktop Score 91%

Progressive Web App Desktop Score 4%

Performance Mobile Score 22%

Best Practices Mobile Score 54%

SEO Mobile Score 92%

Progressive Web App Mobile Score 15%

Page Authority Authority 45%

Domain Authority Domain Authority 61%

Moz Rank 4.5/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 13 Characters

الرئيسية - 2M

Meta Description 141 Characters

الموقع الرسمي للقناة التلفزية الثانية دوزيم يرصد على مدار الساعة الأخبار الوطنية والدولية ويقترح عليكم إعادة لجميع البرامج والنشرات الإخبارية

Effective URL 15 Characters

http://2m.ma/ar

Excerpt Page content

الرئيسية - 2M اغلاق التسجيل ...

Meta Keywords 30 Detected

AR 2M أخبار أخبار القناة الثانية القناة الثانية دوزيم رشيد شو صباحيات برامج دوزيم لكوبل كبور ولحبيب سامحيني أخبار دوزيم اعادة مختفون كي كنتي كي وليتي لحبيبة مي شاهد دوزيم 2M مباشر برامج دوزيم ثمن الحب دوزيم أحلام مراهقين على الثانية آخر المواضيع برامج رمضان 2M مسلسلات دوزيم أخبار المغرب جريدة إلكترونية المغرب رياضة موسي

Keywords Cloud Density

novembre34 نونبر23 sayyidate14 أخبار14 amazigh14 shopping14 المسائية13 soir13 info13 الظهيرة13

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
novembre	34
نونبر	23
sayyidate	14
أخبار	14
amazigh	14
shopping	14
المسائية	13
soir	13
info	13
الظهيرة	13

Google Preview Your look like this in google search result

الرئيسية - 2M

http://2m.ma/ar

Robots.txt File Detected

http://2m.ma/robots.txt

Sitemap.xml File Detected

http://2m.ma/sitemap.xml

Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

Updated: 2017-09-10 / 3 years

Create on: 2005-08-11 / 15 years

Expires on: 2018-08-10 / 30 months 1 days

anouar driss soread 2m

Admin Email: [email protected]

Admin Phone: +212.537533000

Nameservers

srv1-2m.ma

srv2-2m.ma

Page Size Code & Text Ratio

Document Size: ~344.17 KB

Code Size: ~263.17 KB

Text Size: ~81 KB Ratio: 23.54%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Max Potential First Input Delay 140 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 6.5 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 28.4 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 30 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Remove unused CSS Potential savings of 89 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Uses deprecated APIs 1 warning found

Deprecated APIs will eventually be removed from the browser

Serve images in next-gen formats Potential savings of 165 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Does not use HTTPS 115 insecure requests found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

Avoid multiple page redirects Potential savings of 190 ms

Redirects introduce additional delays before the page can be loaded

User Timing marks and measures 16 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Reduce server response times (TTFB) Root document took 860 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 0 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 19 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 100 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 160 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 2.1 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Defer offscreen images Potential savings of 190 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Properly size images Potential savings of 378 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 2.6 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 4.3 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 3,904 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 4.8 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 1.0 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 6 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Avoid an excessive DOM size 2,557 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

First Meaningful Paint 1.0 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 257 requests • 3,904 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 109 resources found

A long cache lifetime can speed up repeat visits to your page

Mobile

Reduce JavaScript execution time 4.9 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Defer offscreen images Potential savings of 55 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Properly size images Potential savings of 36 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 7.4 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 14.0 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 1,884 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 10.0 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 4.0 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 8 chains found

Avoids an excessive DOM size 548 elements

First Meaningful Paint 4.7 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 124 requests • 1,884 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 68 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 340 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 16.8 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive at 16.8 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 90 ms

First Contentful Paint (3G) 8370.5 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Tap targets are sized appropriately 100% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 90.84% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 48 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Uses deprecated APIs 1 warning found

Deprecated APIs will eventually be removed from the browser

Serve images in next-gen formats Potential savings of 19 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Does not use HTTPS 74 insecure requests found

Avoid multiple page redirects Potential savings of 1,260 ms

Redirects introduce additional delays before the page can be loaded

User Timing marks and measures 8 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Reduce server response times (TTFB) Root document took 680 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 330 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Reduce the impact of third-party code Third-party code blocked the main thread for 890 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 1,500 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 301 Moved Permanently
Date: Tue, 26 Nov 2019 13:01:43 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Set-Cookie: __cfduid=dd1624e195dba3bb793721d26a17683931574773303; expires=Thu, 26-Dec-19 13:01:43 GMT; path=/; domain=.2m.ma; HttpOnly
Location: /ar/
Content-Language: ar
X-Varnish: 261820424
Age: 0
Via: 1.1 varnish-v4
X-Cache: MISS
CF-Cache-Status: DYNAMIC
Server: cloudflare
CF-RAY: 53bc0d7a5c9271a7-ORD

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	2m.ma	104.20.14.136	IN	2825
A	2m.ma	104.20.13.136	IN	2825
NS	2m.ma	dnspub3.2m.ma	IN	2892
NS	2m.ma	dnspub2.2m.ma	IN	2892
MX	2m.ma	mailer.2m.ma	IN	2892
MX	2m.ma	mailer2.2m.ma	IN	2892
TXT	2m.ma	MS=9646108F985F72DF79BA93588EA988AAF6B8C598	IN	2892
TXT	2m.ma	v=spf1 mx -all	IN	2892

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

43 2m.ma Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

CloudFlare

Django

Python

Varnish

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments