Tools & Wizards About Us
tower.im screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

tower.im

Tower - ONES 旗下团队协作工具

Page Load Speed

11.2 sec in total

First Response

1.2 sec

Resources Loaded

9.4 sec

Page Rendered

571 ms

tower.im screenshot

About Website

Welcome to tower.im homepage info - get ready to check Tower best content for China right away, or after learning these important things about tower.im

Tower 帮助你更高效的安排工作任务，管理项目进度，沉淀团队知识，让每个人走得更快，让团队走得更远。

Visit tower.im

Key Findings

We analyzed Tower.im page load time and found that the first response time was 1.2 sec and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

tower.im performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

tower.im

1213 ms

tower.im

1636 ms

hk.tower.im

1451 ms

application-a452ef75972a1ffaf150e985a5d84dc5.css

1106 ms

application-8ca2729b0521ff0047d8ab64a61afd46.js

2107 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Tower.im, 81% (29 requests) were made to Hk.tower.im and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Hk.tower.im.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.7 kB (27%)

Content Size

531.1 kB

After Optimization

385.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tower.im main page is 531.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 288.8 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 11.1 kB

  • Original 17.6 kB
  • After minification 15.0 kB
  • After compression 6.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 2.6 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.1 kB or 63% of the original size.

Image Optimization

-0%

Potential reduce by 5 B

  • Original 288.8 kB
  • After minification 288.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Tower images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 66.3 kB

  • Original 130.6 kB
  • After minification 130.6 kB
  • After compression 64.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 66.3 kB or 51% of the original size.

CSS Optimization

-73%

Potential reduce by 68.4 kB

  • Original 94.1 kB
  • After minification 93.6 kB
  • After compression 25.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Tower.im needs all CSS files to be minified and compressed as it can save up to 68.4 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (19%)

Requests Now

31

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tower. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

tower.im

tower.im

1213 ms

tower.im

tower.im

1636 ms

hk.tower.im

hk.tower.im

1451 ms

application-a452ef75972a1ffaf150e985a5d84dc5.css

application-a452ef75972a1ffaf150e985a5d84dc5.css

1106 ms

application-8ca2729b0521ff0047d8ab64a61afd46.js

application-8ca2729b0521ff0047d8ab64a61afd46.js

2107 ms

avatar-fengdahui-bf3cd48caea3f82079d4eab9b88587cb.png

avatar-fengdahui-bf3cd48caea3f82079d4eab9b88587cb.png

810 ms

avatar-joeyyin-aa103ec98b5e33d7a0a954d8ac91286a.png

avatar-joeyyin-aa103ec98b5e33d7a0a954d8ac91286a.png

809 ms

avatar-yxshawn-6f31dd85e626f237f911eea29009b64f.png

avatar-yxshawn-6f31dd85e626f237f911eea29009b64f.png

809 ms

avatar-guoziwei-fe4a0a0fb781415980ba4f227f891eca.png

avatar-guoziwei-fe4a0a0fb781415980ba4f227f891eca.png

807 ms

logo_onework-caa84714229023b78466c90181e56ef1.png

logo_onework-caa84714229023b78466c90181e56ef1.png

1183 ms

logo_pubu-745bd97366246dc7f593b04a704df040.png

logo_pubu-745bd97366246dc7f593b04a704df040.png

1187 ms

logo_wooyun-f637fc0aa50ce6c6e880062dd6a8f2fa.png

logo_wooyun-f637fc0aa50ce6c6e880062dd6a8f2fa.png

1184 ms

logo_upyun-c23940b3024405235157eece771928d2.png

logo_upyun-c23940b3024405235157eece771928d2.png

1182 ms

logo_bearychat-a3a0d8b67ccde185a5646f2b4253527c.png

logo_bearychat-a3a0d8b67ccde185a5646f2b4253527c.png

1483 ms

segmentfault-a2fedc742c12fc96acc9725d9e2cfd3c.png

segmentfault-a2fedc742c12fc96acc9725d9e2cfd3c.png

1556 ms

logo_kuwo-ee5ac6b484788e428441fac8ca598b4d.png

logo_kuwo-ee5ac6b484788e428441fac8ca598b4d.png

1557 ms

logo_hiwork-7850878fa8ebbeb53faf6fe2f0bd3e72.png

logo_hiwork-7850878fa8ebbeb53faf6fe2f0bd3e72.png

1558 ms

wooyun-da923a2a063ac7cfe4ba23c4e2522d61.png

wooyun-da923a2a063ac7cfe4ba23c4e2522d61.png

1559 ms

bg-f650da4d8e3c93c4d42f0b018826c738.jpg

bg-f650da4d8e3c93c4d42f0b018826c738.jpg

772 ms

logo-0dc263aa32b489b62161f437b17bb8e8.png

logo-0dc263aa32b489b62161f437b17bb8e8.png

836 ms

block-chanxiaodui-e6562450eacebdc9c2f4a8aac60abdf5.png

block-chanxiaodui-e6562450eacebdc9c2f4a8aac60abdf5.png

835 ms

block-kanban-720e0a2d11846b7c06db157f0f6ef943.png

block-kanban-720e0a2d11846b7c06db157f0f6ef943.png

838 ms

block-course-10d029a89676ab0ecc49f9df9227cd5d.png

block-course-10d029a89676ab0ecc49f9df9227cd5d.png

838 ms

block-dingtalk-21732eedbb7772e48a44ebd6320a9ee7.png

block-dingtalk-21732eedbb7772e48a44ebd6320a9ee7.png

1158 ms

feature-icons-a7434cbb7539ef65912deb92ec0ea02d.png

feature-icons-a7434cbb7539ef65912deb92ec0ea02d.png

1213 ms

shot-project-0f2aac956995ef51c0c9fcf70306206a.png

shot-project-0f2aac956995ef51c0c9fcf70306206a.png

1795 ms

shot-browser-0be5fc59431947f6f886f8ea32ffda3d.png

shot-browser-0be5fc59431947f6f886f8ea32ffda3d.png

1217 ms

finger-icon-0aab3b3746907bc581fdad22515baaa8.png

finger-icon-0aab3b3746907bc581fdad22515baaa8.png

1217 ms

shot-report-123a30415c5cbd325e3b2aaca9364e82.png

shot-report-123a30415c5cbd325e3b2aaca9364e82.png

1951 ms

logos-it-clients-b85e95427b83928e8a43306f870279c9.png

logos-it-clients-b85e95427b83928e8a43306f870279c9.png

3919 ms

devices-85f17af6036593e9f777c21975a2d0f1.png

devices-85f17af6036593e9f777c21975a2d0f1.png

1864 ms

8AAgABAAAADAAAABYAAAACAAEAAwByAAEABAAAAAIAAAAAeNpjYGBgZACCS5EW58H0VjN1KO0BAEQcBh0AAA==

8AAgABAAAADAAAABYAAAACAAEAAwByAAEABAAAAAIAAAAAeNpjYGBgZACCS5EW58H0VjN1KO0BAEQcBh0AAA==

1 ms

analytics.js

analytics.js

30 ms

collect

collect

15 ms

collect

collect

57 ms

nr-885.min.js

nr-885.min.js

49 ms

Accessibility Review

tower.im accessibility score

67

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tower.im best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tower.im SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tower.im can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tower.im main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

tower.im

Open Graph description is not detected on the main page of Tower. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: