Your Website Score is

Similar Ranking

12
링크프라이스 - 대한민국 제휴마케팅의 강자
linkprice.com
12
LORDFILM.TV - СМОТРЕТЬ ФИЛЬМЫ ОНЛАЙН В ХОРОШЕМ КАЧЕСТВЕ БЕСПЛАТНО
lordfilm5.tv
12
رهام داتک
datak.ir
12
智佳科技网上解放碑,重庆互联网经济大数据监测分析中心,专业从事AI人工智能,数据挖掘,VR虚拟现实,智能硬件,服务机器人,网络营销,360搜索推广,微博,微信,今日头条等新媒体推广,代运营,域名注册,网站备案
cqhot.cn
12
| WWW.GRANDARS.RU
grandars.ru
12
九酷音乐网|好听的歌|网络歌曲|DJ舞曲|流行歌曲大全
9ku.com
12
TELEAMAZONAS - NOTICIAS DE ECUADOR E INTERNACIONALES AL INSTANTE
teleamazonas.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

12 mushroommarket.net Last Updated: 9 months

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

Desktop

Mobile

Performance Desktop Score 76%
Best Practices Desktop Score 46%
SEO Desktop Score 70%
Progressive Web App Desktop Score 31%
Performance Mobile Score 55%
Best Practices Mobile Score 54%
SEO Mobile Score 90%
Progressive Web App Mobile Score 41%
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 33 Characters
中国食用菌商务网-食用菌产业专业门户网站|食用菌网|食用菌栽培技术
Meta Description 170 Characters
中国食用菌商务网是全球食用菌专业门户网站,是服务于中国食用菌产业的一个全方位的网络商务平台,集食用菌资讯、食用菌供求和食用菌技术为一体,发布最新的国内、国际食用菌行业新闻,食用菌市场最新价格变动和海量供应、求购信息,食用菌栽培技术、工厂化、病虫害防治、储藏加工以及食用菌新技术,为食用菌企业和菇农提供一个宝贵的食用菌产品供求、信息共享平台。
Effective URL 25 Characters
http://mushroommarket.net
Excerpt Page content
中国食用菌商务网-食用菌产业专业门户网站|食用菌网|食用菌栽培技术 APP下载  入网须知  资讯投稿  联系我们  English 重要声明:近期发现不法分子及其相关网站打着中国食用菌商务网...
Keywords Cloud Density
向他提问6 擅长领域6 生产栽培4 大球盖菇4 农业农村部4 2019中国4 香菇如何防寒防冻3 基地建设3 平菇喷水3 秀珍菇生长发育对光线条件有何要求3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
向他提问 6
擅长领域 6
生产栽培 4
大球盖菇 4
农业农村部 4
2019中国 4
香菇如何防寒防冻 3
基地建设 3
平菇喷水 3
秀珍菇生长发育对光线条件有何要求 3
Google Preview Your look like this in google search result
中国食用菌商务网-食用菌产业专业门户网站|食用菌网|食用菌栽培技术
http://mushroommarket.net
中国食用菌商务网是全球食用菌专业门户网站,是服务于中国食用菌产业的一个全方位的网络商务平台,集食用菌资讯、食用菌供求和食用菌技术为一体,发布最新的国内、国际食用菌行业新闻,食用菌市场最新价格变动和海量供应、求购信息,食用菌栽培技术、工厂化、病虫害防治、储藏加工以及食用菌新技术,为食用菌企业和菇农提供
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~273.38 KB
Code Size: ~221.3 KB
Text Size: ~52.08 KB Ratio: 19.05%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Serve images in next-gen formats Potential savings of 2,080 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 102 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,240 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 210 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 284 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.
JavaScript execution time 0.7 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
Defer offscreen images Potential savings of 71 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 2,255 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.9 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).
Avoid enormous network payloads Total size was 3,754 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 5.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 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 20 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 3,463 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 107 requests • 3,754 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 93 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 130 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

Mobile

Mobile Screenshot
Total Blocking Time 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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
Defer offscreen images Potential savings of 1,101 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 655 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 6.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.4 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,000 KB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint 3.9 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 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 28 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 681 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)
Preload key requests Potential savings of 900 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 3.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 103 requests • 2,000 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 75 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.2 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) 8111 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 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
Tap targets are not sized appropriately 88% 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 74.08% 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 27 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 692 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 97 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,000 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,790 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 210 KB
Optimized images load faster and consume less cellular data

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, 17 Dec 2019 20:00:06 GMT
Content-Type: text/html
Last-Modified: Tue, 17 Dec 2019 19:54:54 GMT
Connection: keep-alive
Vary: Accept-Encoding
ETag: W/"5df9328e-3ca7f"
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome