Your Website Score is

Similar Ranking

19
OBJETS PUBLICITAIRES MAROC - CADEAUX ENTREPRISE PERSONNALISÉS
marocobjet.ma
19
CAPSTUDIES | CONSEIL EN STRATÉGIE D'ÉTUDES SUPÉRIEURES POUR LA FRANCE
capstudies.ma
19
MON BAC ECO | PRÉPARATION DU BAC ÉCONOMIE EN LIGNE
monbaceco.com
19
MYQR MENU RESTAURANT QR CODE AU MAROC ESSAYEZ GRATUITEMENT
myqr.ma
19
CABINET DENTAIRE RABAT HAY RIAD DR NAWAL MQIRAGE CHIRURGIEN DENTISTE
cabinet-dentaire-dr-mqirage.ma
19
S-STORE
s-store.ma
19
ÉPILATION DÉFINITIVE RABAT CRYOLIPOLYSE RABAT RAJEUNISSEMENT
epilium.ma

Latest Sites

19
ÉPILATION DÉFINITIVE RABAT CRYOLIPOLYSE RABAT RAJEUNISSEMENT
epilium.ma
19
GARAGE SPÉCIALISTE PORSCHE ET SUPERCAR EN HAUT DE FRANCE
legaragedescayoux.fr
29
ACCUEIL - ILYINE PARIS
ilyineparis.com
67
AGENCE WEB À RABAT RÉFÉRENCEMENT SEO MARKETING DIGITAL MAROC
niemeconseil.ma
19
MOROCCO PRIVATE TOUR | LUXURY TOURS LIVE THE AUTHENTICITY IN A LUXURIOUS WAY
moroccoprivatetrip.com
19
CABINET DENTAIRE RABAT HAY RIAD DR NAWAL MQIRAGE CHIRURGIEN DENTISTE
cabinet-dentaire-dr-mqirage.ma
14
COCONUT – SITE N° 1 DE VENTE DE SANDALES COCONUT AU MAROC
coconut.ma

Top Technologies

WordPress
CMS
Google Font API
Font Scripts
Yoast SEO
SEO
Apache
Web Servers
LiteSpeed
Web Servers
WooCommerce
Ecommerce
Font Awesome
Font Scripts
CloudFlare
CDN

19 cabinet-dentaire-dr-mqirage.ma Last Updated: 5 months

Success 55% of passed verification steps
Warning 15% of total warning
Errors 30% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 56%
Best Practices Desktop Score 73%
SEO Desktop Score 92%
Progressive Web App Desktop Score 45%
Performance Mobile Score 10%
Best Practices Mobile Score 67%
SEO Mobile Score 100%
Progressive Web App Mobile Score 50%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 68 Characters
CABINET DENTAIRE RABAT HAY RIAD DR NAWAL MQIRAGE CHIRURGIEN DENTISTE
Meta Description 129 Characters
Cabinet Dentaire Rabat Vous recherchez un dentiste ou un orthodontiste très expérimenté à Rabat. Le meilleur de la santé dentaire
Effective URL 38 Characters
https://cabinet-dentaire-dr-mqirage.ma
Excerpt Page content
Cabinet Dentaire Rabat hay riad Dr Nawal Mqirage Chirurgien Dentiste ...
Keywords Cloud Density
dentaire11 rabat10 cabinet10 soins7 mqirage7 esthétique6 orthodontie6 nous5 dans5 dentiste4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
dentaire 11
rabat 10
cabinet 10
soins 7
mqirage 7
esthétique 6
orthodontie 6
nous 5
dans 5
dentiste 4
Google Preview Your look like this in google search result
CABINET DENTAIRE RABAT HAY RIAD DR NAWAL MQIRAGE CHIRURGIEN
https://cabinet-dentaire-dr-mqirage.ma
Cabinet Dentaire Rabat Vous recherchez un dentiste ou un orthodontiste très expérimenté à Rabat. Le meilleur de la santé dentaire
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: 1970-01-01 / 52 years
Create on: 2021-02-11 / 10 months
Expires on: 2022-02-11 / 2 months 6 days

Nieme conseil
Admin Email: info@niemeconseil.ma
Admin Phone: +212.661896005

Nameservers
ns1.heberfacile.net
ns2.heberfacile.net
Page Size Code & Text Ratio
Document Size: ~176.22 KB
Code Size: ~121.18 KB
Text Size: ~55.04 KB Ratio: 31.23%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

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

Desktop

Desktop Screenshot
First CPU Idle 3.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/).
Speed Index 3.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First Meaningful Paint 1.6 s
First Meaningful Paint measures when the primary content of a page is visible
Efficiently encode images Potential savings of 2,758 KiB
Optimized images load faster and consume less cellular data
Minimize main-thread work 2.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Does not use HTTPS 21 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. 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
Total Blocking Time 130 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused CSS Potential savings of 182 KiB
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
Serve static assets with an efficient cache policy 118 resources found
A long cache lifetime can speed up repeat visits to your page
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Minimize third-party usage Third-party code blocked the main thread for 0 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
Avoid non-composited animations 11 animated elements found
Animations which are not composited can be janky and increase CLS
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint 3.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minify JavaScript Potential savings of 2 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Eliminate render-blocking resources Potential savings of 790 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid an excessive DOM size 1,073 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)
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
Minify CSS Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Keep request counts low and transfer sizes small 143 requests • 6,269 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid chaining critical requests 83 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
Reduce initial server response time Root document took 1,640 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid serving legacy JavaScript to modern browsers Potential savings of 5 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Remove unused JavaScript Potential savings of 230 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
JavaScript execution time 1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Potential savings of 130 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Defer offscreen images Potential savings of 5 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Time to Interactive 3.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted
Max Potential First Input Delay 110 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Serve images in next-gen formats Potential savings of 3,408 KiB
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
Avoid enormous network payloads Total size was 6,269 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 0.418
Cumulative Layout Shift measures the movement of visible elements within the viewport

Mobile

Mobile Screenshot
Reduce initial server response time Root document took 1,690 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize main-thread work 10.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint 5.7 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid enormous network payloads Total size was 6,349 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize third-party usage Third-party code blocked the main thread for 180 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
Defer offscreen images Potential savings of 5 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Eliminate render-blocking resources Potential savings of 4,020 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minify CSS Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Reduce unused JavaScript Potential savings of 251 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Efficiently encode images Potential savings of 2,758 KiB
Optimized images load faster and consume less cellular data
Avoid chaining critical requests 87 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
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
Time to Interactive 16.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce JavaScript execution time 3.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Document uses legible font sizes 97.48% 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
Minify JavaScript Potential savings of 2 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid long main-thread tasks 19 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Avoid an excessive DOM size 1,097 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)
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
First Contentful Paint (3G) 11880 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Cumulative Layout Shift 0.768
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 18.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy 118 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index 12.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Does not use HTTPS 15 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. 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
Properly size images Potential savings of 51 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Max Potential First Input Delay 320 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Reduce unused CSS Potential savings of 182 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Contentful Paint 5.7 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time 1,040 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Keep request counts low and transfer sizes small 144 requests • 6,349 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid serving legacy JavaScript to modern browsers Potential savings of 5 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Serve images in next-gen formats Potential savings of 3,664 KiB
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

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Warning! You have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Only Registered Users

Sign up for see all features and reviews about this site

Login

Comments