Tools & Wizards About Us
officectrl.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

officectrl.com

WebOffice控件 官方网站——支持Word、Excel、Powerpoint、Wps、Visio、Csv和Pdf的Office文档控件

Page Load Speed

10.2 sec in total

First Response

1 sec

Resources Loaded

8.7 sec

Page Rendered

360 ms

officectrl.com screenshot

About Website

Visit officectrl.com now to see the best up-to-date Office Ctrl content for China and also check out these interesting facts you probably never knew about officectrl.com

WebOffice控件是在线编辑Word、Excel、Powerpoint、Wps、Visio、Csv和Pdf的办公文档软件,可以网络远程打开、编辑和保存Word、Excel、Powerpoint、Wps、Visio等文档。

Visit officectrl.com

Key Findings

We analyzed Officectrl.com page load time and found that the first response time was 1 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

officectrl.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value2.164

0/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

officectrl.com

1044 ms

officectrl.com

1012 ms

1.css

340 ms

2.css

981 ms

1.js

1708 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 56% of them (44 requests) were addressed to the original Officectrl.com, 44% (34 requests) were made to Officectrl-x-com.img.addlink.cn. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Officectrl-x-com.img.addlink.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.8 kB (12%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 22.0 kB

  • Original 29.4 kB
  • After minification 25.2 kB
  • After compression 7.3 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 4.1 kB, which is 14% 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 22.0 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 27.4 kB

  • Original 761.1 kB
  • After minification 733.7 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. Office Ctrl images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 90.1 kB

  • Original 396.2 kB
  • After minification 396.2 kB
  • After compression 306.2 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 90.1 kB or 23% of the original size.

CSS Optimization

-26%

Potential reduce by 12.4 kB

  • Original 48.4 kB
  • After minification 48.4 kB
  • After compression 36.0 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. Officectrl.com needs all CSS files to be minified and compressed as it can save up to 12.4 kB or 26% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

39

After Optimization

39

  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Office Ctrl. According to our analytics all requests are already optimized.

Network Requests Diagram

officectrl.com

officectrl.com

1044 ms

officectrl.com

officectrl.com

1012 ms

1.css

1.css

340 ms

2.css

2.css

981 ms

1.js

1.js

1708 ms

2.js

2.js

773 ms

3.js

3.js

2002 ms

visits

visits

690 ms

layer.css

layer.css

452 ms

logo.png

logo.png

235 ms

1@2x.png

1@2x.png

392 ms

2@2x.png

2@2x.png

235 ms

3@2x.png

3@2x.png

233 ms

4@2x.png

4@2x.png

392 ms

new3.gif

new3.gif

448 ms

video.jpg

video.jpg

448 ms

d_download.gif

d_download.gif

449 ms

webax1.png

webax1.png

461 ms

adn.png

adn.png

553 ms

logoall.png

logoall.png

668 ms

phone.png

phone.png

672 ms

qq.png

qq.png

674 ms

tryit.png

tryit.png

677 ms

officectrlmg.png

officectrlmg.png

708 ms

officebbs.png

officebbs.png

778 ms

h1.jpg

h1.jpg

889 ms

h2.jpg

h2.jpg

894 ms

h3.jpg

h3.jpg

898 ms

h4.jpg

h4.jpg

904 ms

h5.jpg

h5.jpg

935 ms

webad1.jpg

webad1.jpg

960 ms

webad2.jpg

webad2.jpg

1072 ms

1.css

1.css

1189 ms

weblist@2x.png

weblist@2x.png

1080 ms

a3@2x.png

a3@2x.png

1083 ms

a1@2x.png

a1@2x.png

1125 ms

a2@2x.png

a2@2x.png

1184 ms

bj@2x.jpg

bj@2x.jpg

1292 ms

t1@2x.png

t1@2x.png

1302 ms

t2@2x.png

t2@2x.png

1308 ms

t3@2x.png

t3@2x.png

1354 ms

t4@2x.png

t4@2x.png

1406 ms

t5@2x.png

t5@2x.png

1416 ms

quote.png

quote.png

1517 ms

3@2x.png

3@2x.png

1252 ms

logo.png

logo.png

1572 ms

2@2x.png

2@2x.png

1290 ms

1@2x.png

1@2x.png

1138 ms

4@2x.png

4@2x.png

1148 ms

new3.gif

new3.gif

1112 ms

video.jpg

video.jpg

1282 ms

d_download.gif

d_download.gif

1324 ms

webax1.png

webax1.png

1317 ms

adn.png

adn.png

1731 ms

logoall.png

logoall.png

1902 ms

phone.png

phone.png

1307 ms

qq.png

qq.png

1345 ms

tryit.png

tryit.png

1355 ms

officectrlmg.png

officectrlmg.png

1344 ms

officebbs.png

officebbs.png

1441 ms

h1.jpg

h1.jpg

1377 ms

h2.jpg

h2.jpg

1381 ms

h3.jpg

h3.jpg

1398 ms

h4.jpg

h4.jpg

1560 ms

h5.jpg

h5.jpg

1576 ms

webad1.jpg

webad1.jpg

3475 ms

webad2.jpg

webad2.jpg

1420 ms

weblist@2x.png

weblist@2x.png

2389 ms

a3@2x.png

a3@2x.png

1580 ms

a1@2x.png

a1@2x.png

1590 ms

a2@2x.png

a2@2x.png

1558 ms

bj@2x.jpg

bj@2x.jpg

1740 ms

t1@2x.png

t1@2x.png

1607 ms

t2@2x.png

t2@2x.png

1654 ms

t3@2x.png

t3@2x.png

1646 ms

t4@2x.png

t4@2x.png

1746 ms

t5@2x.png

t5@2x.png

1793 ms

quote.png

quote.png

1733 ms

Accessibility Review

officectrl.com accessibility score

54

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

officectrl.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

officectrl.com SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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 Officectrl.com 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 Officectrl.com 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

officectrl.com

Open Graph description is not detected on the main page of Office Ctrl. 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: