Tools & Wizards About Us
docwize.com screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

docwize.com

Enterprise Workflow & Legal Data Intelligence Platform | Docwize

Page Load Speed

3 sec in total

First Response

28 ms

Resources Loaded

2.6 sec

Page Rendered

308 ms

docwize.com screenshot

About Website

Visit docwize.com now to see the best up-to-date Docwize content for South Africa and also check out these interesting facts you probably never knew about docwize.com

Docwize delivers enterprise workflow automation and legal data intelligence across legal, finance, construction, and operations. 10TB+ review capability, forensic-level audit architecture, and 25+ yea...

Visit docwize.com

Key Findings

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

Performance Metrics

docwize.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

docwize.com

28 ms

docwize.com

80 ms

style.min.css

62 ms

style.min.css

65 ms

theme.min.css

71 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 63% of them (55 requests) were addressed to the original Docwize.com, 27% (24 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Support.docwize.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Insights.cheymaximcreative.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 437.0 kB (44%)

Content Size

983.2 kB

After Optimization

546.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Docwize.com main page is 983.2 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. 70% of websites need less resources to load. HTML takes 481.7 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 436.2 kB

  • Original 481.7 kB
  • After minification 475.0 kB
  • After compression 45.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 436.2 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 136.0 kB
  • After minification 136.0 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. Docwize images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 433 B

  • Original 301.4 kB
  • After minification 301.4 kB
  • After compression 301.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 360 B

  • Original 64.0 kB
  • After minification 64.0 kB
  • After compression 63.6 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. Docwize.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (60%)

Requests Now

58

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

docwize.com

docwize.com

28 ms

docwize.com

docwize.com

80 ms

style.min.css

style.min.css

62 ms

style.min.css

style.min.css

65 ms

theme.min.css

theme.min.css

71 ms

elementor-icons.min.css

elementor-icons.min.css

71 ms

frontend-lite.min.css

frontend-lite.min.css

54 ms

swiper.min.css

swiper.min.css

49 ms

frontend-lite.min.css

frontend-lite.min.css

66 ms

ecs-style.css

ecs-style.css

81 ms

css

css

59 ms

fontawesome.min.css

fontawesome.min.css

99 ms

solid.min.css

solid.min.css

84 ms

jquery.min.js

jquery.min.js

107 ms

jquery-migrate.min.js

jquery-migrate.min.js

117 ms

ecs_ajax_pagination.js

ecs_ajax_pagination.js

120 ms

ecs.js

ecs.js

121 ms

jquery.min.js

jquery.min.js

41 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

130 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

132 ms

widget-icon-list.min.css

widget-icon-list.min.css

146 ms

animations.min.css

animations.min.css

148 ms

hello-frontend.min.js

hello-frontend.min.js

145 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

128 ms

webpack.runtime.min.js

webpack.runtime.min.js

148 ms

frontend-modules.min.js

frontend-modules.min.js

160 ms

waypoints.min.js

waypoints.min.js

157 ms

core.min.js

core.min.js

191 ms

frontend.min.js

frontend.min.js

186 ms

ecspro.js

ecspro.js

183 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

184 ms

hooks.min.js

hooks.min.js

175 ms

i18n.min.js

i18n.min.js

195 ms

frontend.min.js

frontend.min.js

192 ms

elements-handlers.min.js

elements-handlers.min.js

238 ms

chat.min.js

chat.min.js

71 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

67 ms

waypoints

waypoints

330 ms

Insight_logo_transparent2.svg

Insight_logo_transparent2.svg

133 ms

partner-2.webp

partner-2.webp

1095 ms

control-logo.svg

control-logo.svg

84 ms

track-logo.svg

track-logo.svg

88 ms

jvent-logo.svg

jvent-logo.svg

82 ms

hero-background.webp

hero-background.webp

243 ms

insight-text.svg

insight-text.svg

92 ms

section-background-shape.webp

section-background-shape.webp

159 ms

line-animation.svg

line-animation.svg

89 ms

section-image-icon.svg

section-image-icon.svg

92 ms

MicrosoftTeams-image-4-1.png

MicrosoftTeams-image-4-1.png

97 ms

MicrosoftTeams-image-5-2.png

MicrosoftTeams-image-5-2.png

98 ms

MicrosoftTeams-image-2-1.png

MicrosoftTeams-image-2-1.png

98 ms

MicrosoftTeams-image-3-1.png

MicrosoftTeams-image-3-1.png

126 ms

bottom-section-background.webp

bottom-section-background.webp

243 ms

insight-icon-light.svg

insight-icon-light.svg

135 ms

insight-book.webp

insight-book.webp

244 ms

bottom-section-background-image-scaled.webp

bottom-section-background-image-scaled.webp

277 ms

Insight_logo_transparent.svg

Insight_logo_transparent.svg

237 ms

footer-sub-logo.svg

footer-sub-logo.svg

239 ms

DocWize_Insight_Orginal.jpg

DocWize_Insight_Orginal.jpg

370 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

46 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

62 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

64 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

65 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

65 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

63 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

66 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf

185 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf

144 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

66 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

68 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

67 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

68 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf

148 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf

146 ms

fa-solid-900.woff

fa-solid-900.woff

215 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

90 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

91 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

92 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

139 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

140 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

140 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

140 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

141 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

141 ms

chat.css%27%29%3B

chat.css%27%29%3B

3 ms

chat.css

chat.css

34 ms

main.js

main.js

34 ms

partner-2.webp

partner-2.webp

1046 ms

Accessibility Review

docwize.com accessibility score

85

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.

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

docwize.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

docwize.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docwize.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Docwize.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

docwize.com

Open Graph data is detected on the main page of Docwize. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: