Your Website Score is

Similar Ranking

20
DIGIFINEX DIGITAL ASSETS EXCHANGE - BITCOIN, ETHEREUM, LITECOIN, BLOCKCHAIN ASSETS TRADING PLATFORM.
digifinex.com
20
WWW.ANDHRABANK.IN
andhrabank.in
20
PUBLIC SERVICE COMMISSION, WEST BENGAL
pscwbapplication.in
20

Latest Sites

24
THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ
noithatmanhhe.vn
19
SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP
nhacanhothongminh.com
16
CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM
crypto-mining.biz
57
99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING
999dice.com
19
RELANDICE BOT FOR 999DICE
relandice.com
23
❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !
baophong.vn
51
ONE MORE STEP
seeking.com

Top Technologies

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

20 myedenred.fr Last Updated: 9 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 74%
Best Practices Desktop Score 92%
SEO Desktop Score 80%
Progressive Web App Desktop Score 35%
Performance Mobile Score 26%
Best Practices Mobile Score 92%
SEO Mobile Score 91%
Progressive Web App Mobile Score 37%
Page Authority Authority 32%
Domain Authority Domain Authority 28%
Moz Rank 3.2/10
Bounce Rate Rate 0%
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 20 Characters
https://myedenred.fr
Excerpt Page content
We're sorry but ExB doesn't work properly without JavaScript enabled. Please enable it to continue.
Keywords Cloud Density
sorry1 doesn1 work1 properly1 without1 javascript1 enabled1 please1 enable1 continue1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
sorry 1
doesn 1
work 1
properly 1
without 1
javascript 1
enabled 1
please 1
enable 1
continue 1
Google Preview Your look like this in google search result
myedenred.fr
https://myedenred.fr
We're sorry but ExB doesn't work properly without JavaScript enabled. Please enable it to continue.
Robots.txt File Detected
Sitemap.xml File Detected
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 / 51 years
Create on: 2013-03-09 / 8 years
Expires on: 1970-01-01 / 617 months 18 days

SAFEBRANDS SAFEBRANDS SAFEBRANDS SAFEBRANDS SAFEBRANDS ,FR FR FR FR
Registrar Email: [email protected]
Registrar Address: Pôle Média de la Belle de Mai 37 Rue Guibal 13356 MARSEILLE CEDEX 03 Edenred 166-180, boulevard Gabriel Peri 92245 Malakoff EDENRED 166-180, boulevard Gabriel Peri 92245 Malakoff SAFEBRANDS Pole Media de la Belle de Mai, 37 rue Guibal 13356 Marseille ,

Nameservers
a.ns.mailclub.fr
[195.64.164.8
2a03:1780:1:12:a::8]
b.ns.mailclub.eu
c.ns.mailclub.com
Page Size Code & Text Ratio
Document Size: ~4.78 KB
Code Size: ~3.5 KB
Text Size: ~1.28 KB Ratio: 26.82%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

MyEdenred Web MyEdenred Web

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)
Param name
MyEdenred Web
Param theme_color
#162056
Param background_color
#162056
Param display
fullscreen
Param scope
/
Param start_url
/
Manifest is not valid
Your manifest are missing some important params, read more in Web App Manifest

Desktop

Desktop Screenshot
Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.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).
Avoids enormous network payloads Total size was 2,545 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
robots.txt is not valid 35 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
First Contentful Paint 1.4 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 2 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
Avoids an excessive DOM size 231 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.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 54 requests • 2,545 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 4 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 170 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 2.3 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 10.1 s
A fast page load over a cellular network ensures a good mobile user experience
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
Remove unused CSS Potential savings of 178 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
Serve images in next-gen formats Potential savings of 872 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
Server response times are low (TTFB) Root document took 510 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
Efficiently encode images Potential savings of 407 KB
Optimized images load faster and consume less cellular data
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
Total Blocking Time 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.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
Properly size images Potential savings of 473 KB
Serve images that are appropriately-sized to save cellular data and improve load time

Mobile

Mobile Screenshot
Server response times are low (TTFB) Root document took 100 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,290 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 240 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,420 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 4.6 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
Speed Index 6.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 8.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).
Avoids enormous network payloads Total size was 1,955 KB
Large network payloads cost users real money and are highly correlated with long load times
robots.txt is not valid 35 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Minimize main-thread work 6.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 5.6 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 2 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
Avoids an excessive DOM size 138 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 7.5 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 54 requests • 1,955 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 5 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 770 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 10.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 at 10.5 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 260 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
First Contentful Paint (3G) 11321.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.53% 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 179 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
Serve images in next-gen formats Potential savings of 417 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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

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 200 OK
Cache-Control: public,max-age=31536000
Content-Length: 1912
Content-Type: text/html
Content-Encoding: gzip
Last-Modified: Tue, 24 Dec 2019 14:32:11 GMT
Accept-Ranges: bytes
ETag: "07e4ee66bad51:0:dtagent10181191119154660fPZS"
Vary: Accept-Encoding
Server: Microsoft-IIS/10.0
Set-Cookie: dtCookie=v_4_srv_1_sn_76599F83F574628522A3CAE9BF665251_perc_100000_ol_0_mul_1; Path=/; Domain=.myedenred.fr
X-Powered-By: ASP.NET
X-OneAgent-JS-Injection: true
X-ruxit-JS-Agent: true
Set-Cookie: ARRAffinity=d891add96ebecf07473c3cba5c97609bec357d1b1b8d6e586a10372be88a68bc;Path=/;HttpOnly;Domain=myedenred.fr
Date: Tue, 07 Jan 2020 04:45:30 GMT
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome