Tools & Wizards About Us
quickfinder.com screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% 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

  • 79

    SEO

    Google-friendlier than
    40% of websites

quickfinder.com

Checkpoint Quickfinder | Thomson Reuters | Tax & Accounting | Thomson Reuters

Page Load Speed

7.1 sec in total

First Response

212 ms

Resources Loaded

5.8 sec

Page Rendered

1.1 sec

quickfinder.com screenshot

About Website

Welcome to quickfinder.com homepage info - get ready to check Quickfinder best content right away, or after learning these important things about quickfinder.com

Our practical tax aids from Thomson Reuters Quickfinder supply accurate and useful information in a down-to-earth and concise writing style.

Visit quickfinder.com

Key Findings

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

Performance Metrics

quickfinder.com performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value19.0 s

0/100

10%

TBT (Total Blocking Time)

Value19,000 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.672

8/100

15%

TTI (Time to Interactive)

Value31.4 s

0/100

10%

Network Requests Diagram

quickfinder.com

212 ms

96 ms

quickfinder

625 ms

schemaFunctions.min.js

148 ms

highlight.js

155 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Quickfinder.com, 20% (16 requests) were made to App-data.gcs.trstatic.net and 15% (12 requests) were made to Tax.thomsonreuters.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Store.tax.thomsonreuters.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 630.5 kB (54%)

Content Size

1.2 MB

After Optimization

533.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Quickfinder.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. Only a small number of websites need less resources to load. Javascripts take 668.3 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 226.8 kB

  • Original 261.5 kB
  • After minification 210.1 kB
  • After compression 34.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 51.4 kB, which is 20% 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 226.8 kB or 87% of the original size.

Image Optimization

-13%

Potential reduce by 23.1 kB

  • Original 179.4 kB
  • After minification 156.3 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. Obviously, Quickfinder needs image optimization as it can save up to 23.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-57%

Potential reduce by 379.8 kB

  • Original 668.3 kB
  • After minification 667.8 kB
  • After compression 288.5 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 379.8 kB or 57% of the original size.

CSS Optimization

-1%

Potential reduce by 725 B

  • Original 54.3 kB
  • After minification 54.3 kB
  • After compression 53.5 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. Quickfinder.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 54 (76%)

Requests Now

71

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

quickfinder.com

quickfinder.com

212 ms

96 ms

quickfinder

quickfinder

625 ms

schemaFunctions.min.js

schemaFunctions.min.js

148 ms

highlight.js

highlight.js

155 ms

main.css

main.css

364 ms

head.js

head.js

666 ms

otSDKStub.js

otSDKStub.js

275 ms

adrum-21.4.0.3405.js

adrum-21.4.0.3405.js

133 ms

clientlibs.min.css

clientlibs.min.css

55 ms

clientlibs.min.js

clientlibs.min.js

219 ms

jquery.min.js

jquery.min.js

220 ms

utils.min.js

utils.min.js

215 ms

granite.min.js

granite.min.js

194 ms

tracking-clientlibs.min.js

tracking-clientlibs.min.js

197 ms

main.js

main.js

782 ms

pagestyle-clientlibs.min.css

pagestyle-clientlibs.min.css

203 ms

68d13ac7-d0f0-4279-827a-39220fe2e40e.json

68d13ac7-d0f0-4279-827a-39220fe2e40e.json

374 ms

launch-180ff4990fd5.min.js

launch-180ff4990fd5.min.js

1099 ms

gtm.js

gtm.js

825 ms

tr2638595-01a-2880x710.jpg

tr2638595-01a-2880x710.jpg

681 ms

location

location

928 ms

knowledge2017-regular-webfont.woff

knowledge2017-regular-webfont.woff

274 ms

knowledge2017-medium-webfont.woff

knowledge2017-medium-webfont.woff

274 ms

knowledge2017-light-webfont.woff

knowledge2017-light-webfont.woff

382 ms

knowledge2017-black-webfont.woff

knowledge2017-black-webfont.woff

381 ms

proview-videostill.jpeg

proview-videostill.jpeg

304 ms

token.json

token.json

382 ms

cart.json

cart.json

1774 ms

5.js

5.js

461 ms

3.js

3.js

1229 ms

4.js

4.js

459 ms

6.js

6.js

457 ms

7.js

7.js

458 ms

57.js

57.js

457 ms

37.js

37.js

459 ms

14.js

14.js

458 ms

27.js

27.js

457 ms

EXa35dfe7785b14dcda254a6b5011ecf46-libraryCode_source.min.js

EXa35dfe7785b14dcda254a6b5011ecf46-libraryCode_source.min.js

255 ms

AppMeasurement_Module_AudienceManagement.min.js

AppMeasurement_Module_AudienceManagement.min.js

485 ms

6si.min.js

6si.min.js

1463 ms

hotjar-13668.js

hotjar-13668.js

992 ms

json

json

1387 ms

analytics.js

analytics.js

924 ms

otBannerSdk.js

otBannerSdk.js

161 ms

api.js

api.js

1414 ms

insight.min.js

insight.min.js

1369 ms

bat.js

bat.js

1366 ms

js

js

381 ms

RCd21e60c7058541e2b4cf50152255ef5f-source.min.js

RCd21e60c7058541e2b4cf50152255ef5f-source.min.js

707 ms

RC827dbe9d1a2d4c3a9919a18449e227aa-source.min.js

RC827dbe9d1a2d4c3a9919a18449e227aa-source.min.js

787 ms

en.json

en.json

868 ms

conversion_async.js

conversion_async.js

788 ms

elqCfg.min.js

elqCfg.min.js

684 ms

fbevents.js

fbevents.js

507 ms

modules.2be88a2123e5e486752f.js

modules.2be88a2123e5e486752f.js

392 ms

collect

collect

210 ms

collect

collect

476 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

298 ms

otFlat.json

otFlat.json

134 ms

otPcCenter.json

otPcCenter.json

173 ms

getuidj

getuidj

519 ms

c.6sc.co

c.6sc.co

408 ms

progress-events.js

progress-events.js

237 ms

215515565692587

215515565692587

193 ms

507 ms

svrGP

svrGP

485 ms

svrGP

svrGP

412 ms

svrGP

svrGP

498 ms

svrGP

svrGP

510 ms

img.gif

img.gif

420 ms

ga-audiences

ga-audiences

379 ms

40 ms

details

details

7 ms

22 ms

svrgp.aspx

svrgp.aspx

152 ms

svrGP

svrGP

159 ms

264 ms

RC515a6a393efb42668fd2a62afc940f40-source.min.js

RC515a6a393efb42668fd2a62afc940f40-source.min.js

56 ms

adrum-ext.281eccdb0a28fe3b4dbfbf942f8b88ed.js

adrum-ext.281eccdb0a28fe3b4dbfbf942f8b88ed.js

52 ms

img.gif

img.gif

214 ms

Accessibility Review

quickfinder.com accessibility score

67

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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

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

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

SEO Factors

quickfinder.com SEO score

79

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

High

Image elements do not have [alt] attributes

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

quickfinder.com

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