Tools & Wizards About Us
digita.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

digita.com

Digita Software for Accountants and Tax Practitioners

Page Load Speed

1.7 sec in total

First Response

183 ms

Resources Loaded

1.1 sec

Page Rendered

403 ms

digita.com screenshot

About Website

Click here to check amazing Digita content for United Kingdom. Otherwise, check out these important facts you probably never knew about digita.com

Automate your simpler compliance tasks and maximise your efficiency with our integrated accounting software for accountants. Learn more today.

Visit digita.com

Key Findings

We analyzed Digita.com page load time and found that the first response time was 183 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

digita.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value2,560 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

digita.com

183 ms

114 ms

otSDKStub.js

34 ms

core_style.css

129 ms

light_style.css

142 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Digita.com, 46% (32 requests) were made to Tax.thomsonreuters.co.uk and 16% (11 requests) were made to App-data.gcs.trstatic.net. The less responsive or slowest element that took the longest time to load (423 ms) relates to the external source Tax.thomsonreuters.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.2 kB (10%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digita.com main page is 2.1 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. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 130.8 kB

  • Original 155.5 kB
  • After minification 105.0 kB
  • After compression 24.7 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 50.5 kB, which is 32% 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 130.8 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 8.9 kB

  • Original 448.9 kB
  • After minification 440.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. Digita images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 55.2 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.2 MB

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

-10%

Potential reduce by 18.2 kB

  • Original 181.4 kB
  • After minification 179.4 kB
  • After compression 163.2 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. Digita.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 45 (78%)

Requests Now

58

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

digita.com

digita.com

183 ms

114 ms

otSDKStub.js

otSDKStub.js

34 ms

core_style.css

core_style.css

129 ms

light_style.css

light_style.css

142 ms

magnific-popup.css

magnific-popup.css

81 ms

vendor.css

vendor.css

95 ms

layouts.css

layouts.css

105 ms

style-uk.css

style-uk.css

115 ms

ewp-header.min.css

ewp-header.min.css

165 ms

ewp-footer.css

ewp-footer.css

170 ms

uk-fix.v2.css

uk-fix.v2.css

137 ms

TRCommunityWidgets.js

TRCommunityWidgets.js

79 ms

jquery.min.js

jquery.min.js

193 ms

jquery-migrate.min.js

jquery-migrate.min.js

191 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

212 ms

jquery.magnific-initialize.js

jquery.magnific-initialize.js

263 ms

head_scripts.min.js

head_scripts.min.js

227 ms

main.css

main.css

45 ms

head.js

head.js

47 ms

open-web.0.7.10.min.css

open-web.0.7.10.min.css

245 ms

uk-fix.v2.css

uk-fix.v2.css

326 ms

collapse.js

collapse.js

326 ms

bundle.js

bundle.js

341 ms

privacy-notice.js

privacy-notice.js

340 ms

ewp-header.js

ewp-header.js

341 ms

open-web.0.7.10.min.js

open-web.0.7.10.min.js

338 ms

ewp-footer.js

ewp-footer.js

423 ms

main.js

main.js

51 ms

e4e4fd28-100a-4e1c-8728-6b94dc274000.json

e4e4fd28-100a-4e1c-8728-6b94dc274000.json

27 ms

location

location

61 ms

otBannerSdk.js

otBannerSdk.js

21 ms

xwhEiBv1HU9C21muwxPTXU.jpg

xwhEiBv1HU9C21muwxPTXU.jpg

200 ms

TR1871796_1230x400_01G-V2.png

TR1871796_1230x400_01G-V2.png

304 ms

open-web-sprites.0.7.10.svg

open-web-sprites.0.7.10.svg

160 ms

194918F.jpg

194918F.jpg

175 ms

iframe_api

iframe_api

272 ms

xwhEiBv1HU9C21muwxPTXU.js

xwhEiBv1HU9C21muwxPTXU.js

99 ms

9Fh1F8XPEkYw5VNBPyZ4A9.js

9Fh1F8XPEkYw5VNBPyZ4A9.js

202 ms

knowledge2017-regular-webfont.woff

knowledge2017-regular-webfont.woff

94 ms

knowledge2017-medium-webfont.woff

knowledge2017-medium-webfont.woff

94 ms

knowledge2017-light-webfont.woff

knowledge2017-light-webfont.woff

185 ms

knowledge2017-black-webfont.woff

knowledge2017-black-webfont.woff

199 ms

knowledge-bold-webfont.woff

knowledge-bold-webfont.woff

95 ms

knowledge-light-webfont.woff

knowledge-light-webfont.woff

94 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

166 ms

knowledge-regular-webfont.woff

knowledge-regular-webfont.woff

94 ms

Ca9QLRkUrtFaeLi_bjOs9WqJihBB9IBB.jpg

Ca9QLRkUrtFaeLi_bjOs9WqJihBB9IBB.jpg

261 ms

0.js

0.js

201 ms

1.js

1.js

128 ms

4.js

4.js

157 ms

15.js

15.js

179 ms

shim.css

shim.css

124 ms

form-core.js

form-core.js

147 ms

81d5f392a969718815dd5f.jpg

81d5f392a969718815dd5f.jpg

211 ms

xwhEiBv1HU9C21muwxPTXU

xwhEiBv1HU9C21muwxPTXU

143 ms

elqCfg.min.js

elqCfg.min.js

174 ms

9Fh1F8XPEkYw5VNBPyZ4A9

9Fh1F8XPEkYw5VNBPyZ4A9

21 ms

runtime~main-7cfe5b991f8998b11779881f5769bbe9.js

runtime~main-7cfe5b991f8998b11779881f5769bbe9.js

51 ms

main-9c07bee87619db3865ec02655fc94ea3.js

main-9c07bee87619db3865ec02655fc94ea3.js

54 ms

www-widgetapi.js

www-widgetapi.js

35 ms

9Fh1F8XPEkYw5VNBPyZ4A9.json

9Fh1F8XPEkYw5VNBPyZ4A9.json

8 ms

vendors~access-code~player~polyfills~unreleased-b17f5f35d7830a75324ee1cd5b5c535b.js

vendors~access-code~player~polyfills~unreleased-b17f5f35d7830a75324ee1cd5b5c535b.js

9 ms

vendors~polyfills-997e30b96ba07291aa086b1496553fa0.js

vendors~polyfills-997e30b96ba07291aa086b1496553fa0.js

9 ms

polyfills-21b89d124255973c8a69d3d6c9517218.js

polyfills-21b89d124255973c8a69d3d6c9517218.js

17 ms

xwhEiBv1HU9C21muwxPTXU.json

xwhEiBv1HU9C21muwxPTXU.json

12 ms

vendors~player~player-pomo~unreleased-ab12c5410a30202855ccd359eb0e7f98.js

vendors~player~player-pomo~unreleased-ab12c5410a30202855ccd359eb0e7f98.js

37 ms

vendors~access-code~player-pomo~whitelisted-embed-61d05a035333aec4c9f4860e28e0b0c5.js

vendors~access-code~player-pomo~whitelisted-embed-61d05a035333aec4c9f4860e28e0b0c5.js

28 ms

vendors~player-pomo-701ee626bc6396c34baa5fbf11fe3f98.js

vendors~player-pomo-701ee626bc6396c34baa5fbf11fe3f98.js

16 ms

player-pomo-0d1c572c6bf350fa8c24158eff8e885f.css

player-pomo-0d1c572c6bf350fa8c24158eff8e885f.css

34 ms

Accessibility Review

digita.com accessibility score

90

Accessibility Issues

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

Buttons do not have an accessible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

digita.com SEO score

86

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Digita.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 Digita.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

digita.com

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