Your Website Score is

Similar Ranking

6
首 页 - 广东文灿压铸股份有限公司
wencan.com
6
景洪市人民政府
jhs.gov.cn
6
ACCOUNT SUSPENDED
sucolectivo.com
6
EVERGREEN HEALTH
evergreenhealth.ca
5
优茄折扣-领优惠券,购物更便宜。
yoqie.com

Latest Sites

53
站长之家 - 站长资讯-我们致力于为中文网站提供动力!
chinaz.com
1
21
没有找到站点
meijukan.com

Top Technologies

Nginx
Web Servers
Windows Server
Operating Systems
Apache
Web Servers
Google Web Server
Web Servers
Microsoft ASP NET
Web Frameworks
CloudFlare
CDN
Twitter Bootstrap
Web Frameworks

6 wencan.com Last Updated: 2 years

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

Desktop

Mobile

Performance Desktop Score 83%
Best Practices Desktop Score 62%
SEO Desktop Score 78%
Progressive Web App Desktop Score 31%
Performance Mobile Score 78%
Best Practices Mobile Score 69%
SEO Mobile Score 87%
Progressive Web App Mobile Score 41%
Page Authority Authority 32%
Domain Authority Domain Authority 8%
Moz Rank 3.2/10
Bounce Rate Rate 0%
Title Tag 18 Characters
首 页 - 广东文灿压铸股份有限公司
Meta Description 12 Characters
广东文灿压铸股份有限公司
Effective URL 21 Characters
http://www.wencan.com
Excerpt Page content
首 页 - 广东文灿压铸股份有限公司  股票代码 603348 0757- 85119488 ...
Meta Keywords 1 Detected
Keywords Cloud Density
人才招聘3 滤清器系统3 filters3 components3 pump3 body2 文灿集团股份有限公司2 wencan2 valve2 品质技术2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
人才招聘 3
滤清器系统 3
filters 3
components 3
pump 3
body 2
文灿集团股份有限公司 2
wencan 2
valve 2
品质技术 2
Google Preview Your look like this in google search result
首 页 - 广东文灿压铸股份有限公司
http://www.wencan.com
广东文灿压铸股份有限公司
Robots.txt File No Found
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~15.61 KB
Code Size: ~9.06 KB
Text Size: ~6.55 KB Ratio: 41.96%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimation Traffic and Earnings

157
Unique Visits
Daily
290
Pages Views
Daily
$0
Income
Daily
4,396
Unique Visits
Monthly
8,265
Pages Views
Monthly
$0
Income
Monthly
50,868
Unique Visits
Yearly
97,440
Pages Views
Yearly
$0
Income
Yearly

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

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

Desktop

Desktop Screenshot
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 305 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 46 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,270 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 400 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 52 KB
Optimized images load faster and consume less cellular data
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.3 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 409 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.6 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 695 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 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 7 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 258 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 46 requests • 695 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 33 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

Mobile

Mobile Screenshot
Server response times are low (TTFB) Root document took 360 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,400 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 22 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.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 323 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 7.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 2.0 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 833 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 2.0 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 133 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.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 30 requests • 833 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 27 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.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
First Contentful Paint (3G) 3484 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 310 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 30 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
Avoid multiple page redirects Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

1,813,755

Global Rank

1,813,755

Global
Traffic
Search

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Tue, 13 Sep 2022 05:59:27 GMT
Server: Apache
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
Set-Cookie: PHPSESSID=1c1824a747b2f1c37ef53c691965102c; path=/
Vary: User-Agent,Accept-Encoding
Content-Encoding: gzip
Content-Length: 20
Content-Type: text/html;charset=utf-8;
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Add extension to Chrome