Your Website Score is

Similar Ranking

11
MAILSBOXES - SERVICE DE DOMICILIATION D'ENTREPRISE 100% EN LIGNE
mailsboxes.com
11
AGENCIA DE VIAJE A MARRAKECH MARRUECOS, VIAJE AL DESIERTO Y LAS MONTAÑAS
sahara-viajes-marruecos.com
11
VIAMINEDZ : ALGERIE ACTUALIÉS, INFORMATIONS, PHOTOS, ANNONCES ALGÉRIE
vitaminedz.com
11
P2G : ACCUEIL
p2g.fr
11
ARMURERIE EN LIGNE, ACHAT FUSIL, CARABINE, ARMES DE CHASSE ET TIR SPORTIF
meyson.fr
11
STREETART-VM - L'ART EST DANS LA RUE, MOI AUSSI!
streetart-vm.com

Latest Sites

24
REFERENCEMENT GOOGLE GRATUIT, REFERENCEMENT AUTOMATIQUE EN 1ÈRE PAGE !
referencement-google-gratuit.com
34
PEIGNOIR PERSONNALISÉ - LE JARDIN D'ELÉONORE
peignoir-brode-personnalise.fr
24
CHAMBRE FROIDE, VITRINE RÉFRIGÉRÉE, CONGÉLATEUR
procold.fr
39
JEAN JOSIA | CUISINE, SALLE DE BAIN & DRESSING SUR MESURE
jeanjosia.com
4
LOCAL PRODUCTS > 100% FRENCH RIVIERA
local-fine-foods.com
31
ACCUEIL - ZANA
zana-workshop.com
35
HGL DYNAMICS : ACQUISITION MULTIVOIES, MESURE DE DYNAMIQUE.
hgl-dynamics.fr

Top Technologies

Google Font API
Font Scripts
Apache
Web Servers
WordPress
CMS
Font Awesome
Font Scripts
Yoast SEO
SEO
Nginx
Web Servers
Twitter Bootstrap
Web Frameworks
Google Tag Manager
Tag Managers

11 larose.ma Last Updated: 7 months

Success 39% of passed verification steps
Warning 23% of total warning
Errors 38% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 59%
Best Practices Desktop Score 67%
SEO Desktop Score 91%
Progressive Web App Desktop Score 36%
Performance Mobile Score 46%
Best Practices Mobile Score 67%
SEO Mobile Score 85%
Progressive Web App Mobile Score 42%
Page Authority Authority 33%
Domain Authority Domain Authority 18%
Moz Rank 3.3/10
Bounce Rate Rate 0%
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 16 Characters
http://larose.ma
Google Preview Your look like this in google search result
larose.ma
http://larose.ma
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~1 B
Code Size: ~NAN B
Text Size: ~1 B Ratio: 100.00%

Social Data

Delicious Total: 0
Facebook Total: 121,937
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

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

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 1.7 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/).
Remove unused JavaScript Potential savings of 130 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
Does not use HTTPS 1 insecure request 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
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
Largest Contentful Paint 3.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 142 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
Remove unused CSS Potential savings of 84 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
Estimated Input Latency 10 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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Eliminate render-blocking resources Potential savings of 1,210 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 59 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small 82 requests • 873 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Avoid an excessive DOM size 1,143 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)
Avoids enormous network payloads Total size was 873 KiB
Large network payloads cost users real money and are highly correlated with long load times
Initial server response time was short Root document took 340 ms
Keep the server response time for the main document short because all other requests depend on it
Cumulative Layout Shift 1.536
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid multiple page redirects Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded
Preload key requests Potential savings of 210 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 9 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve static assets with an efficient cache policy 44 resources found
A long cache lifetime can speed up repeat visits to your page
Minimizes main-thread work 1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay 130 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 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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 chaining critical requests 46 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
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 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
Properly size images Potential savings of 85 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Time to Interactive 3.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible
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
Efficiently encode images Potential savings of 27 KiB
Optimized images load faster and consume less cellular data

Mobile

Mobile Screenshot
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 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
Preload key requests Potential savings of 1,890 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Enable text compression Potential savings of 59 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Total Blocking Time 370 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Estimated Input Latency 110 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
Max Potential First Input Delay 550 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First CPU Idle 6.1 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/).
Eliminate render-blocking resources Potential savings of 2,400 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint 3.4 s
First Contentful Paint marks the time at which the first text or image is painted
Minimize third-party usage Third-party code blocked the main thread for 70 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
Time to Interactive 8.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Document uses legible font sizes 74.79% 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
Keep request counts low and transfer sizes small 50 requests • 893 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Properly size images Potential savings of 66 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
Remove unused JavaScript Potential savings of 129 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Remove unused CSS Potential savings of 51 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 images in next-gen formats Potential savings of 238 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
First Meaningful Paint 3.8 s
First Meaningful Paint measures when the primary content of a page is visible
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
Avoids an excessive DOM size 786 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)
Avoids enormous network payloads Total size was 893 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 19 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
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
First Contentful Paint (3G) 6720 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Initial server response time was short Root document took 320 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
Largest Contentful Paint 6.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Does not use HTTPS 1 insecure request 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
Efficiently encode images Potential savings of 47 KiB
Optimized images load faster and consume less cellular data
Minimize main-thread work 3.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.189
Cumulative Layout Shift measures the movement of visible elements within the viewport
Defer offscreen images Potential savings of 18 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Speed Index 6.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve static assets with an efficient cache policy 35 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid multiple page redirects Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded
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
Reduce JavaScript execution time 2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

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
Warning! Your description is not 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
Warning! Your website is not SSL secured (HTTPS).
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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
Congratulations! You not have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
larose.co Already Registered
larose.us Already Registered
larose.com Available Buy Now!
larose.org Already Registered
larose.net Already Registered
lrose.ma Available Buy Now!
oarose.ma Available Buy Now!
parose.ma Available Buy Now!

Information Server

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


						
DNS Records DNS Resource Records associated with a hostname
View DNS Records