Your Website Score is

Similar Ranking

47
WEBSITE VALUE CALCULATOR AND WEB INFORMATION
websiteoutlook.com
47
INTERNET SPEED TEST | FAST.COM
fast.com
47
ERROR PAGE | EBAY
ebay.ie
47
THE WORK MANAGEMENT PLATFORM | PIPEFY
pipefy.com
47
MIS MARCADORES: RESULTADOS DE FÚTBOL EN DIRECTO, FÚTBOL EN VIVO
mismarcadores.com
47
企查查-企业工商信息查询系统_查企业_查老板_查关系就上企查查!
qichacha.com
47
URLAUB: BIS 40% RABATT BEIM MARKTFÜHRER | AB-IN-DEN-URLAUB.DE
ab-in-den-urlaub.de

Latest Sites

19
PINOY MOVIES - WATCH PINOY MOVIES ONLINE---
cineko.to
14
FINYA LIMITED
finyalimited.com
14
CADOCINVESTMENT.COM | AUSTRALIAN INVESTMENT COMPANY
cadocinvestment.com
14
NGF LEGAL – CORPORATE LAWYER AGENCY
ngflegal.com
14
GLOBAL LOGISTICS AUSTRALIA | GLOBAL LOGISTICS LIMITED
globallogisticslimited.com
50
THE GUY R COOK REPORT BLOG
guyrcook.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

47 mafengwo.cn Last Updated: 12 months

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

Desktop

Mobile

Performance Desktop Score 89%
Best Practices Desktop Score 54%
SEO Desktop Score 70%
Progressive Web App Desktop Score 31%
Performance Mobile Score 52%
Best Practices Mobile Score 54%
SEO Mobile Score 92%
Progressive Web App Mobile Score 48%
Page Authority Authority 56%
Domain Authority Domain Authority 56%
Moz Rank 5.6/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 29 Characters
旅游攻略,自由行,自助游攻略,旅游社交分享网站 - 马蜂窝
Meta Description 77 Characters
马蜂窝!靠谱的旅游攻略,自由行,自助游分享社区,海量旅游景点图片、游记、交通、美食、购物等自由行旅游攻略信息,马蜂窝旅游网获取自由行,自助游攻略信息更全面
Effective URL 22 Characters
http://www.mafengwo.cn
Excerpt Page content
旅游攻略,自由行,自助游攻略,旅游社交分享网站 - 马蜂窝 首页 目的地 旅游攻略 去旅行 ...
Meta Keywords 3 Detected
Keywords Cloud Density
图片来自于5 荣誉出品5 此目的地共收藏了5 旅游攻略2 mafengwo2 火车时刻表2 酒店预订2 加入马蜂窝2 晒韩国街拍赢巴黎欧莱雅时尚大礼2 09月25日2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
图片来自于 5
荣誉出品 5
此目的地共收藏了 5
旅游攻略 2
mafengwo 2
火车时刻表 2
酒店预订 2
加入马蜂窝 2
晒韩国街拍赢巴黎欧莱雅时尚大礼 2
09月25日 2
Google Preview Your look like this in google search result
旅游攻略,自由行,自助游攻略,旅游社交分享网站 - 马蜂窝
http://www.mafengwo.cn
马蜂窝!靠谱的旅游攻略,自由行,自助游分享社区,海量旅游景点图片、游记、交通、美食、购物等自由行旅游攻略信息,马蜂窝旅游网获取自由行,自助游攻略信息更全面
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~71.34 KB
Code Size: ~69.13 KB
Text Size: ~2.21 KB Ratio: 3.10%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Total Blocking Time 20 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
Defer offscreen images Potential savings of 3,552 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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 2,553 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.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).
Avoid enormous network payloads Total size was 11,707 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.3 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.6 s
First Contentful Paint marks the time at which the first text or image is painted
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
Avoid chaining critical requests 5 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 1,186 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)
Minify JavaScript Potential savings of 14 KB
Minifying JavaScript files can reduce payload sizes and script parse time
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 100 requests • 11,707 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Uses efficient cache policy on static assets 5 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 90 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.0 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
Remove unused CSS Potential savings of 43 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 9,815 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
Does not use HTTPS 48 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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
Reduce server response times (TTFB) Root document took 830 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 280 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 202 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

Mobile

Mobile Screenshot
Uses efficient cache policy on static assets 4 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.6 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
First Contentful Paint (3G) 6818 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
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
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 92.82% 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 25 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 160 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
Avoid multiple page redirects Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded
Does not use HTTPS 2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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
Reduce server response times (TTFB) Root document took 1,880 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,900 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 16 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 10 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 200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 153 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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 13 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 7.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.5 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 844 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 3.4 s
First Contentful Paint marks the time at which the first text or image is painted
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
Avoid chaining critical requests 3 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 142 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)
Minify JavaScript Potential savings of 75 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 45 requests • 844 KB
To set budgets for the quantity and size of page resources, add a budget.json file

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 405 Method Not Allowed
Server: openresty
Content-Type: text/html; charset=UTF-8
X-Sid: 2.205
X-Pid: 124791
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Date: Sun, 08 Dec 2019 16:41:15 GMT
Connection: keep-alive
Set-Cookie: PHPSESSID=f5l2rhnumgs60pke9r7l9d14p3; path=/; domain=.mafengwo.cn; HttpOnly
Set-Cookie: mfw_uuid=5ded27ab-dccb-33e5-e38e-0634a8c11a68; expires=Mon, 07-Dec-2020 16:41:15 GMT; Max-Age=31536000; path=/; domain=.mafengwo.cn
Set-Cookie: oad_n=a%3A3%3A%7Bs%3A3%3A%22oid%22%3Bi%3A1029%3Bs%3A2%3A%22dm%22%3Bs%3A15%3A%22www.mafengwo.cn%22%3Bs%3A2%3A%22ft%22%3Bs%3A19%3A%222019-12-09+00%3A41%3A15%22%3B%7D; expires=Sun, 15-Dec-2019 16:41:15 GMT; Max-Age=604800; path=/; domain=.mafengwo.cn
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome