Your Website Score is

Similar Ranking

2
質問・疑問に答えるQ&AサイトOKWAVE
okwave.jp
2
МУЖСКОЙ ЖУРНАЛ MAXIM ONLINE. ОФИЦИАЛЬНЫЙ САЙТ ЛУЧШЕГО МУЖСКОГО ЖУРНАЛА MAXIM.
maximonline.ru
2
LAMIAREPORT.GR
lamiareport.gr
2
MY.COM — COMMUNICATION AND ENTERTAINMENT SERVICES: MYMAIL, MAPS.ME, AND GAMES.
my.com
2
HABER ZAMANI | HABERLER ZAMANINDA OKUNUR
haberzamani.com
2
魅族官网 - 魅族 16XS 手机,极边全面屏 三摄长续航
meizu.com

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

2 haofang.net Last Updated: 10 months

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

Desktop

Mobile

Performance Desktop Score 79%
Best Practices Desktop Score 85%
SEO Desktop Score 80%
Progressive Web App Desktop Score 46%
Performance Mobile Score 53%
Best Practices Mobile Score 54%
SEO Mobile Score 92%
Progressive Web App Mobile Score 48%
Page Authority Authority 36%
Domain Authority Domain Authority 10%
Moz Rank 3.6/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 30 Characters
【北京二手房网|北京租房网|北京房产信息网】- 北京优优好房
Meta Description 89 Characters
北京优优好房提供真实的租房、二手房、整租、公寓等北京房产信息,及时的房地产新闻资讯,每日实时更新全城数千中介公司上万经纪人最新挂牌的租售房源,免费查询北京房产信息,就到优优好房。
Effective URL 22 Characters
https://bj.haofang.net
Excerpt Page content
 【北京二手房网|北京租房网|北京房产信息网】- 北京优优好房 选择城市 ...
Keywords Cloud Density
查看更多推荐>>4 2室2厅3 申请友链2 3室1厅2 vr看房2 2室1厅2 珺悦国际2 扫码下载优优好房app2 微信登录2 门头沟区二手房1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
查看更多推荐>> 4
2室2厅 3
申请友链 2
3室1厅 2
vr看房 2
2室1厅 2
珺悦国际 2
扫码下载优优好房app 2
微信登录 2
门头沟区二手房 1
Google Preview Your look like this in google search result
【北京二手房网|北京租房网|北京房产信息网】- 北京优优好房
https://bj.haofang.net
北京优优好房提供真实的租房、二手房、整租、公寓等北京房产信息,及时的房地产新闻资讯,每日实时更新全城数千中介公司上万经纪人最新挂牌的租售房源,免费查询北京房产信息,就到优优好房。
Robots.txt File Detected
Sitemap.xml File No Found
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: 2017-05-16 / 3 years
Create on: 2013-06-14 / 7 years
Expires on: 2019-06-14 / 15 months 20 days

Chengdu West Dimension Digital Technology Co., Ltd. ,
Registrar Whois Server: whois.west263.com
Registrar URL: http://Chengdu West Dimension Digital Technology Co., LTD

Nameservers
NS1.MYHOSTADMIN.NET
NS2.MYHOSTADMIN.NET
Page Size Code & Text Ratio
Document Size: ~49.29 KB
Code Size: ~30.59 KB
Text Size: ~18.7 KB Ratio: 37.94%

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
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
Speed Index 3.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 0.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,856 KB
Large network payloads cost users real money and are highly correlated with long load times
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
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 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 9 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 995 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.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 50 requests • 1,856 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 45 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 30 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.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
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 1,298 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
Reduce server response times (TTFB) Root document took 1,500 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 100 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 648 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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Mobile

Mobile Screenshot
First CPU Idle 5.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,006 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 7.0 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.7 s
First Contentful Paint marks the time at which the first text or image is painted
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
Avoids an excessive DOM size 397 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 2.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 64 requests • 1,006 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 54 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 2,600 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) 5520 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 1,690 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 82.78% 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
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Serve images in next-gen formats Potential savings of 456 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 1 insecure request 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
Avoid multiple page redirects Potential savings of 1,410 ms
Redirects introduce additional delays before the page can be loaded
Reduce server response times (TTFB) Root document took 1,350 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 760 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 43 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 2,310 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 5.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 314 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
Speed Index 9.6 s
Speed Index shows how quickly the contents of a page are visibly populated

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
Server: Tengine
Date: Tue, 26 Nov 2019 08:23:29 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=jmaod379sm39tvfre70400q5b1; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Pragma: no-cache
Set-Cookie: citydomain=%25E5%258C%2597%25E4%25BA%25AC%7Cbj.haofang.net; expires=Wed, 27-Nov-2019 08:23:29 GMT; Max-Age=86400; path=/
Cache-control: private
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome