Your Website Score is
SEO Rank : 23 Website URL: lagrima.fr Last Updated: 2 months
Success
55% of passed verification steps
Warning
30% of total warning
Errors
15% of total errors, require fast action
Share
Estimation Traffic and Earnings
0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 21%
Domain Authority
Domain Authority 16%
Moz Rank
2.1/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
62 Characters
LAGRIMA.FR • ???? BOUTIQUE DE TATOUAGE ÉPHÉMÈRE FRANÇAISE
Meta Description
245 Characters
Lagrima.fr ???? est une boutique dans le but d'apporter de la nouveauté sur votre peau et un nouveau style a part entière. Plus de 500 tatouages sont disponibles sur notre boutique en ligne : unique et de meilleur qualité que des standards.
Effective URL
18 Characters
https://lagrima.fr
Excerpt
Page content
Lagrima.fr • ???? Boutique De Tatouage éphémère Française
COVID 2019 : Livraison gratuite confirmée en France dans votre boîte aux lettres ????
Ignorer
Skip to content
...
Google Preview
Your look like this in google search result
LAGRIMA.FR • ???? BOUTIQUE DE TATOUAGE ÉPHÉMÈRE FRANÇAI
https://lagrima.fr
Lagrima.fr ???? est une boutique dans le but d'apporter de la nouveauté sur votre peau et un nouveau style a part entière. Plus de 500 tatouages
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~125.44 KB
Code Size: ~98.09 KB
Text Size: ~27.35 KB Ratio: 21.80%
Social Data
Delicious
Total: 0
Facebook
Total: 66
Google
Total: 0
Linkedin
Total: 0
Pinterest
Total: 0
Stumbleupon
Total: 0
Tumblr
Total: 0
Vk
Total: 0
Technologies
PWA - Manifest
Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest
Desktop
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
Eliminate render-blocking resources
Potential savings of 580 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Meaningful Paint
0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce initial server response time
Root document took 1,600 ms
Keep the server response time for the main document short because all other requests depend on it
Cumulative Layout Shift
0.027
Cumulative Layout Shift measures the movement of visible elements within the viewport
Properly size images
Potential savings of 238 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
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
Avoids enormous network payloads
Total size was 1,266 KiB
Large network payloads cost users real money and are highly correlated with long load times
Uses efficient cache policy on static assets
2 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
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
First CPU Idle
0.9 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/).
Minify CSS
Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Avoid chaining critical requests
24 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
909 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 Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid long main-thread tasks
2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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
Max Potential First Input Delay
40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve images in next-gen formats
Potential savings of 375 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
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Keep request counts low and transfer sizes small
42 requests • 1,266 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Time to Interactive
0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Remove unused CSS
Potential savings of 75 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
Remove unused JavaScript
Potential savings of 48 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimizes main-thread work
1.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint
2.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Speed Index
3.4 s
Speed Index shows how quickly the contents of a page are visibly populated
JavaScript execution time
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Mobile
Max Potential First Input Delay
210 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed Index
8.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Remove unused JavaScript
Potential savings of 48 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Document uses legible font sizes
99.71% 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
First Contentful Paint (3G)
6072 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Contentful Paint
3.2 s
First Contentful Paint marks the time at which the first text or image is painted
Minify CSS
Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
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
Total Blocking Time
260 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Cumulative Layout Shift
0.095
Cumulative Layout Shift measures the movement of visible elements within the viewport
Tap targets are not sized appropriately
93% 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 1,720 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve images in next-gen formats
Potential savings of 319 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
Avoids enormous network payloads
Total size was 914 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
First CPU Idle
4.4 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/).
Largest Contentful Paint
9.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce JavaScript execution time
1.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint
3.2 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused CSS
Potential savings of 76 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
Properly size images
Potential savings of 80 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Time to Interactive
6.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Minimize main-thread work
3.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Uses efficient cache policy on static assets
2 resources found
A long cache lifetime can speed up repeat visits to your page
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
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
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Avoid an excessive DOM size
909 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)
Reduce initial server response time
Root document took 1,350 ms
Keep the server response time for the main document short because all other requests depend on it
Estimated Input Latency
50 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 chaining critical requests
24 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
Keep request counts low and transfer sizes small
36 requests • 914 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid long main-thread tasks
14 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
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
Congratulations! You not have broken links
View links
| First 20 Links | Relationship | HTTP Status |
| A Propos | Internal Link | 200 |
| Suivez votre colis | Internal Link | 200 |
| FAQ / Contact | Internal Link | 200 |
| S’inscrire | Internal Link | 200 |
| Connexion | Internal Link | 200 |
| Compte | Internal Link | 200 |
| Lagrima.fr - Tatouage Ephémère | Internal Link | 200 |
| Tatouages | Internal Link | 200 |
| Homme | Internal Link | 200 |
| Femme | Internal Link | 200 |
| Attrape-rêve | Internal Link | 200 |
| Henné | Internal Link | 200 |
| Or & argenté | Internal Link | 200 |
| Animaux | Internal Link | 200 |
| Loup | Internal Link | 200 |
| Papillon | Internal Link | 200 |
| Nature | Internal Link | 200 |
| Fleurs | Internal Link | 200 |
| Rose | Internal Link | 200 |
| Cultures | Internal Link | 200 |
Alexa Rank
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| lagrima.co | Already Registered |
| lagrima.us | Already Registered |
| lagrima.com | Already Registered |
| lagrima.org | Already Registered |
| lagrima.net | Already Registered |
| lgrima.fr | Already Registered |
| oagrima.fr | Already Registered |
| pagrima.fr | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Fri, 08 Jan 2021 06:52:31 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
set-cookie: wp_woocommerce_session_4cc43269ad4789390c4289b186eef7b8=10ff266b8d4e44f22c3186177d57b408%7C%7C1610261551%7C%7C1610257951%7C%7C08f5d04ac4e8a29b090c2198c343262c; expires=Sun, 10-Jan-2021 06:52:31 GMT; Max-Age=172800; path=/; secure; HttpOnly
cache-control: max-age=0
expires: Fri, 08 Jan 2021 06:52:31 GMT
age: 0
x-cache: MISS
server: o2switch-PowerBoost-v3
content-encoding: gzip
Click to Add/Show Comments