Ele.me - SEO Checker - Website Review

Your Website Score is

Similar Ranking

国联资源网_中国领先的B2B电子商务集群,高效的链商资源整合服务网络

ibicn.com

REVOLVE (リボルブ)で、有名デザイナーズブランドの洋服をショッピング

revolveclothing.co.jp

VOITURE AU MAROC - VOITURE OCCASION AU MAROC - ANNONCES MOTEUR.MA

moteur.ma

مكتبة نور - تحميل كتب PDF

noor-book.com

BEST WIFI BROADBAND & INTERNET SERVICE PROVIDER (ISP) IN INDIA | TIKONA INFINET PRIVATE LIMITED

tikona.in

DOWNLOAD FREE SOFTWARE FOR WINDOWS - JALECO.COM

jaleco.com

نماشا - سرویس رایگان اشتراک ویدیو

namasha.com

Latest Sites

ACUITY FUNDING

acuityfunding.com

sharenow126.com

MASUK

gm066.com

恭喜，站点创建成功！

51278.cc

m.fun8899jk.com

JOBIFY

jobify2u.com

PROLIKE

prolikeid.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

31 ele.me Last Updated: 1 year

Success 78% of passed verification steps

Warning 7% of total warning

Errors 15% of total errors, require fast action

Mobile

Performance Desktop Score 82%

Best Practices Desktop Score 92%

SEO Desktop Score 90%

Progressive Web App Desktop Score 50%

Performance Mobile Score 82%

Best Practices Mobile Score 92%

SEO Mobile Score 88%

Progressive Web App Mobile Score 48%

Page Authority Authority 0%

Domain Authority Domain Authority 0%

Moz Rank 0.0/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 19 Characters

饿了么-网上订餐_外卖_饿了么订餐官网

Meta Description 76 Characters

“饿了么”2008年创立于上海，是中国领先的本地生活平台。截至目前，饿了么在线外卖交易平台已覆盖全国2000个城市，加盟餐厅130万家，用户量达2.6亿

Effective URL 18 Characters

https://www.ele.me

Excerpt Page content

饿了么-网上订餐_外卖_饿了么订餐官网

Meta Keywords 1 Detected

饿了么，外卖

Google Preview Your look like this in google search result

饿了么-网上订餐_外卖_饿了么订餐官网

https://www.ele.me

“饿了么”2008年创立于上海，是中国领先的本地生活平台。截至目前，饿了么在线外卖交易平台已覆盖全国2000个城市，加盟餐厅130万家，用户量达2.6亿

Robots.txt File Detected

http://ele.me/robots.txt

Sitemap.xml File Detected

http://ele.me/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~3 KB

Code Size: ~2.65 KB

Text Size: ~358 B Ratio: 11.65%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Desktop

Reduce server response times (TTFB) Root document took 910 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 390 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 340 KB

Optimized images load faster and consume less cellular data

Total Blocking Time 10 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 0.1 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 148 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 2.7 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 0.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).

Avoids enormous network payloads Total size was 1,343 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 0.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 0.7 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 6 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 76 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 0.7 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 22 requests • 1,343 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 80 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 0.7 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

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

Serve images in next-gen formats Potential savings of 851 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

Mobile

Server response times are low (TTFB) Root document took 240 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,630 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 340 KB

Optimized images load faster and consume less cellular data

Total Blocking Time 130 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

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 111 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 5.7 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 2.6 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,343 KB

Large network payloads cost users real money and are highly correlated with long load times

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

First Contentful Paint 2.5 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 6 chains found

Avoids an excessive DOM size 76 elements

First Meaningful Paint 2.5 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 22 requests • 1,343 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 300 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.9 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

Estimated Input Latency 10 ms

First Contentful Paint (3G) 4893 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 not sized appropriately 63% 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 100% 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

Serve images in next-gen formats Potential savings of 851 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

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
Access-Control-Allow-Origin: *
Age: 47
Ali-Swift-Global-Savetime: 1577244662
Cache-Control: max-age=60, s-maxage=300
Content-Encoding: gzip
Content-Length: 1609
Content-Md5: tfXL/ZBHkZCeORHgG9lqeQ==
Content-Type: text/html
Eagleid: 6525b79515772447090366270e
Server: Sopush/0.22.0
Strict-Transport-Security: max-age=31536000
Timing-Allow-Origin: *
Vary: Accept-Encoding
Via: cache17.l2et15-1[37,200-0,M], cache7.l2et15-1[37,0], cache13.cn1576[0,200-0,H], cache1.cn1576[1,0]
X-Cache: HIT TCP_MEM_HIT dirn:-2:-2
X-Echo-Requestid: 784673A091AF4A7A8FFF2EE856699C8D|1577244709018
X-Oss-Hash-Crc64ecma: 11188213720475217130
X-Oss-Object-Type: Normal
X-Oss-Request-Id: 5E02D7F6D6B6FD3634507DBA
X-Oss-Server-Time: 2
X-Oss-Storage-Class: Standard
X-Sopush-Cache-Control: public, s-maxage=30, stale-while-revalidate=30
X-Sopush-Cache-Status: miss
X-Source-Scheme: https
X-Swift-Cachetime: 300
X-Swift-Savetime: Wed, 25 Dec 2019 03:31:02 GMT
Date: Wed, 25 Dec 2019 03:31:49 GMT

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	ele.me	106.15.160.220	IN	238
A	ele.me	106.14.48.241	IN	238
NS	ele.me	ns2.alibabadns.com	IN	82235
NS	ele.me	ns1.alibabadns.com	IN	82235
MX	ele.me	mx1.ele.me	IN	300
MX	ele.me	mx2.ele.me	IN	300
TXT	ele.me	MS=ms29866390	IN	300
TXT	ele.me	847cdba8-d986-4c81-b154-0c21614b4fd9-1435133909700	IN	300
TXT	ele.me	v=spf1 ip4:116.236.204.5 ip4:112.65.166.114 ip4:140.207.236.2 include:spf.sendcloud.org ~all	IN	300

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

31 ele.me Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments