Your Website Score is

Similar Ranking

50
♛ ????-????????????????????????ℝ???? •ᴹᴬ ★ ✔
g-software.ma
50
KEYLIANCE - RACHAT DE CRÉDITS EN FRANCE & OUTRE-MER
keyliance.fr
50
LIVRAISON FLEURS FRAÎCHES 7J/7 EN 4H | INTERFLORA
interflora.fr
50
TELEDISCOUNT
telediscount.fr
50
LOCATIONS DE VACANCES, LOGEMENTS, EXPÉRIENCES ET LIEUX - AIRBNB
airbnb.fr
50
THE TIMES OF NORTHWEST INDIANA | MUNSTER, IN | NWITIMES.COM
nwitimes.com
50
APPRENDRE LE THAÏ AVEC L'ASSOCIATION CULTURELLE FRANCO-THAÏE
acft-paris.com

Latest Sites

23
CUSTOMS BRIDGE, LES INNOV'ACTEURS DE LA DOUANE
customsbridge.fr
19
SEARCHBESTFLIGHTS - BEST TRAVEL DEALS
searchbestflights.com
14
ACCUEIL - GREEN COM' COMMUNICATION RESPONSABLE
greencom.fr
28
EPIBAG - SAC À PAIN PUBLICITAIRE
epibag.com
32
PARIS DEPANNAGE INFORMATIQUE | RÉPARATION PC À DOMICILE
paris-depannage.fr
24
CENTRE DE FORMATION COMPTABLE À DISTANCE, COURS COMPTABILITÉ NICE - ENCG
encg-formation.com
14
DRIVER FORMATION
driver-formation.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

50 interflora.fr Last Updated: 1 year

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

Desktop

Mobile

Performance Desktop Score 64%
Best Practices Desktop Score 60%
SEO Desktop Score 92%
Progressive Web App Desktop Score 45%
Performance Mobile Score 12%
Best Practices Mobile Score 60%
SEO Mobile Score 83%
Progressive Web App Mobile Score 50%
Page Authority Authority 44%
Domain Authority Domain Authority 62%
Moz Rank 4.4/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 55 Characters
LIVRAISON FLEURS FRAÎCHES 7J/7 EN 4H | INTERFLORA
Meta Description 144 Characters
Faire livrer un superbe bouquet de fleurs rapidement par un des artisans fleuristes INTERFLORA. Bouquet dés 24,90€ remis en main propre sous 4H.
Effective URL 25 Characters
https://www.interflora.fr
Excerpt Page content
Livraison fleurs fraîches 7j/7 en 4h | Interflora Questions fréquentes |  Contactez-nous | 0825 20 20 20(0,20€/min + prix appel) |  Suivi de commande Nouveau&nb...
Meta Keywords 1 Detected
Keywords Cloud Density
fleurs51 livraison31 vous25 pour18 fleuriste18 interflora17 votre15 dans15 bouquet15 avec13
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
fleurs 51
livraison 31
vous 25
pour 18
fleuriste 18
interflora 17
votre 15
dans 15
bouquet 15
avec 13
Google Preview Your look like this in google search result
LIVRAISON FLEURS FRAÎCHES 7J/7 EN 4H | INTERFLORA
https://www.interflora.fr
Faire livrer un superbe bouquet de fleurs rapidement par un des artisans fleuristes INTERFLORA. Bouquet dés 24,90€ remis en main propre sous 4H.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~229.63 KB
Code Size: ~204.82 KB
Text Size: ~24.81 KB Ratio: 10.80%

Social Data

Delicious Total: 0
Facebook Total: 407,598
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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the 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
Serve static assets with an efficient cache policy 55 resources found
A long cache lifetime can speed up repeat visits to your page
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
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Avoid chaining critical requests 11 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Efficiently encode images Potential savings of 353 KiB
Optimized images load faster and consume less cellular data
Avoid serving legacy JavaScript to modern browsers Potential savings of 82 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
Total Blocking Time 350 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Eliminate render-blocking resources Potential savings of 430 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint 1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce JavaScript execution time 1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Cumulative Layout Shift 0.083
Cumulative Layout Shift measures the movement of visible elements within the viewport
Estimated Input Latency 40 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
User Timing marks and measures 10 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Avoid long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimize third-party usage Third-party code blocked the main thread for 50 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
Enable text compression Potential savings of 97 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Remove unused JavaScript Potential savings of 531 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
Defer offscreen images Potential savings of 502 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid an excessive DOM size 931 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)
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
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Keep request counts low and transfer sizes small 172 requests • 4,157 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Remove unused CSS Potential savings of 261 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
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Serve images in next-gen formats Potential savings of 986 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 4,157 KiB
Large network payloads cost users real money and are highly correlated with long load times
Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First CPU Idle 4.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/).
Time to Interactive 5.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive

Mobile

Mobile Screenshot
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Max Potential First Input Delay 1,030 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Reduce JavaScript execution time 10.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimize main-thread work 13.8 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
First Contentful Paint 4.7 s
First Contentful Paint marks the time at which the first text or image is painted
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
Time to Interactive 38.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Remove unused JavaScript Potential savings of 523 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Total Blocking Time 4,040 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid serving legacy JavaScript to modern browsers Potential savings of 53 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
Serve static assets with an efficient cache policy 57 resources found
A long cache lifetime can speed up repeat visits to your page
Serve images in next-gen formats Potential savings of 4,531 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
Eliminate render-blocking resources Potential savings of 2,220 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,190 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 5.9 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
Efficiently encode images Potential savings of 20 KiB
Optimized images load faster and consume less cellular data
User Timing marks and measures 3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Speed Index 11.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Enable text compression Potential savings of 97 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Cumulative Layout Shift 0.197
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 6.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Defer offscreen images Potential savings of 3,318 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid non-composited animations 14 animated elements found
Animations which are not composited can be janky and increase CLS
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
Document uses legible font sizes 99.4% 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 238 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
Avoid enormous network payloads Total size was 7,664 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce the impact of third-party code Third-party code blocked the main thread for 900 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 chaining critical requests 8 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 CPU Idle 19.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/).
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Estimated Input Latency 440 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 161 requests • 7,664 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Tap targets are not sized appropriately 73% 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
First Contentful Paint (3G) 9358 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

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
Congratulations! Your title is 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
Congratulations! Your Domain Authority is good
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
interflora.co Already Registered
interflora.us Available Buy Now!
interflora.com Already Registered
interflora.org Already Registered
interflora.net Already Registered
iterflora.fr Available Buy Now!
mnterflora.fr Available Buy Now!
knterflora.fr Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
content-type: text/html;charset=UTF-8
content-length: 31631
date: Wed, 17 Mar 2021 09:29:07 GMT
vary: Accept-Encoding
cache-control: max-age=0, s-maxage=432000
expires: Tue, 16 Mar 2021 18:45:39 GMT
last-modified: Tue, 16 Mar 2021 18:45:39 GMT
x-fstrz: o,c
content-encoding: gzip
x-gen-id: 783eaec90d30b9c1f07caf65338a12c7
server: fasterize
x-unique-id: dde95c6b46c6e2e9946c419c3af3a784
x-cache: Miss from cloudfront
via: 1.1 071c6d250f90381986ebbec31df7b7e4.cloudfront.net (CloudFront)
x-amz-cf-pop: BRU50-C1
x-amz-cf-id: Cuh4MLIuJoDf0ynIr9h6poKhQKKTsr3WodDhd45jdSGaTiqL9QI6Vg==
DNS Records DNS Resource Records associated with a hostname
View DNS Records