Your Website Score is

Similar Ranking

49
ONLINE APOTHEKE FÜR DEUTSCHLAND ▷ SHOP APOTHEKE
shop-apotheke.com
49
WEATHER - AUSTRALIA 7 DAY FORECASTS AND WEATHER RADAR - WEATHERZONE
weatherzone.com.au
49
LES VENTES PRIVÉES DE GRANDES MARQUES AVEC SHOWROOMPRIVE
showroomprive.com
49
UNIVERSITY OF JOHANNESBURG
uj.ac.za
49
SHOPGOODWILL.COM
shopgoodwill.com
49
ALLDATASHEET.COM - DATASHEET SEARCH SITE FOR ELECTRONIC COMPONENTS AND SEMICONDUCTORS AND OTHER SEMICONDUCTORS.
alldatasheet.com
49
ETEXTBOOKS | RENT OR BUY ONLINE TEXTBOOKS | VITALSOURCE
vitalsource.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

49 tower.im Last Updated: 10 months

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

Desktop

Mobile

Performance Desktop Score 79%
Best Practices Desktop Score 92%
SEO Desktop Score 100%
Progressive Web App Desktop Score 73%
Performance Mobile Score 57%
Best Practices Mobile Score 92%
SEO Mobile Score 100%
Progressive Web App Mobile Score 74%
Page Authority Authority 51%
Domain Authority Domain Authority 24%
Moz Rank 5.1/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 21 Characters
TOWER - 提升协作效率,打造高效团队
Meta Description 51 Characters
Tower 帮助你更高效的安排工作任务,管理项目进度,沉淀团队知识,让每个人走得更快,让团队走得更远。
Effective URL 16 Characters
https://tower.im
Excerpt Page content
Tower - 提升协作效率,打造高效团队 功能 价格 快速入门 样板间 资源 登录 免费体验 提升协...
Keywords Cloud Density
tower13 免费体验3 联系我们2 提高效率2 这条只要1 真的幫助我們很多~1 項目功能動態功能都非常實用1 homam1 因为要做方案还要做内容1 每个文档都会很清楚把要做的内容和图片都展现出来1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
tower 13
免费体验 3
联系我们 2
提高效率 2
这条只要 1
真的幫助我們很多~ 1
項目功能動態功能都非常實用 1
homam 1
因为要做方案还要做内容 1
每个文档都会很清楚把要做的内容和图片都展... 1
Google Preview Your look like this in google search result
TOWER - 提升协作效率,打造高效团队
https://tower.im
Tower 帮助你更高效的安排工作任务,管理项目进度,沉淀团队知识,让每个人走得更快,让团队走得更远。
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~28.45 KB
Code Size: ~25.65 KB
Text Size: ~2.81 KB Ratio: 9.86%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Tower Tower Tower

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)
Param name
Tower
Param short_name
Tower
Param description
Tower - 深受用户喜爱的团队协作工具
Param start_url
.
Param display
standalone
Param theme_color
#44acb6
Param background_color
#ffffff

Desktop

Desktop Screenshot
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 45 requests • 4,350 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 3 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 230 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 1.3 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 20 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 72 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 1,209 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,780 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 930 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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 140 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
Speed Index 2.6 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 4,336 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 1.1 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 245 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)

Mobile

Mobile Screenshot
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 39 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 30 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 5.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.2 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 2,906 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.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 213 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 4.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 35 requests • 2,919 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 3 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 1,010 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.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
First Contentful Paint (3G) 6398 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 440 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 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
Remove unused CSS Potential savings of 41 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 49 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
Server response times are low (TTFB) Root document took 350 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 3,440 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 210 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 1,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 1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

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
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
Date: Thu, 28 Nov 2019 08:30:12 GMT
X-Frame-Options: ALLOW-FROM https://im.dingtalk.com
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-TWR-VERSION: 19.34.16
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 2018-11-28 16:30:12 +0800
Set-Cookie: _tower2_session=55091d55bbd45377d205848eeacf2c43; domain=.tower.im; path=/; secure; HttpOnly
X-Request-Id: c05637d5-5f88-4d5e-b4af-80f96b2cc232
X-Runtime: 0.019041
Set-Cookie: uid=rBACK13fhZTB9UX0Kv1XAg==; expires=Fri, 27-Nov-20 08:30:12 GMT; path=/
P3P: policyref="/w3c/p3p.xml", CP="CUR ADM OUR NOR STA NID"
Via: cache40.l2et2[44,0], cache5.jp1[106,0], cache4.us16[239,0]
Timing-Allow-Origin: *, *
EagleId: 2ff6119815749298122872033e, 2ff6119815749298122872033e
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome