Tools & Wizards About Us
swiftcase.co.uk screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

swiftcase.co.uk

SwiftCase - Workflow Automation for UK Service Businesses

Page Load Speed

3.8 sec in total

First Response

259 ms

Resources Loaded

2.7 sec

Page Rendered

871 ms

swiftcase.co.uk screenshot

About Website

Welcome to swiftcase.co.uk homepage info - get ready to check Swift Case best content for United Kingdom right away, or after learning these important things about swiftcase.co.uk

SwiftCase is where UK service businesses run their case work, from first contact to closed file. Workflow automation, case management, document generation and reporting in one platform.

Visit swiftcase.co.uk

Key Findings

We analyzed Swiftcase.co.uk page load time and found that the first response time was 259 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

swiftcase.co.uk performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value2,870 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.215

58/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

swiftcase.co.uk

259 ms

swiftcase.co.uk

308 ms

www.swiftcase.co.uk

959 ms

js

83 ms

formidableforms.css

13 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 74% of them (70 requests) were addressed to the original Swiftcase.co.uk, 16% (15 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (959 ms) belongs to the original domain Swiftcase.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.0 kB (8%)

Content Size

1.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Swiftcase.co.uk main page is 1.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 957.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 136.1 kB

  • Original 161.0 kB
  • After minification 155.3 kB
  • After compression 24.9 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 136.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 1.7 kB

  • Original 957.3 kB
  • After minification 955.6 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. Swift Case images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.2 kB

  • Original 571.0 kB
  • After minification 571.0 kB
  • After compression 565.8 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

-5%

Potential reduce by 11.0 kB

  • Original 230.2 kB
  • After minification 230.1 kB
  • After compression 219.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. Swiftcase.co.uk has all CSS files already compressed.

Requests Breakdown

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

Requests Now

59

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

swiftcase.co.uk

swiftcase.co.uk

259 ms

swiftcase.co.uk

swiftcase.co.uk

308 ms

www.swiftcase.co.uk

www.swiftcase.co.uk

959 ms

js

js

83 ms

formidableforms.css

formidableforms.css

13 ms

icons.css

icons.css

20 ms

global.css

global.css

23 ms

style.min.css

style.min.css

23 ms

bootstrap.min.css

bootstrap.min.css

26 ms

bootstrap-glyphicons.min.css

bootstrap-glyphicons.min.css

32 ms

header-footer-elementor.css

header-footer-elementor.css

32 ms

elementor-icons.min.css

elementor-icons.min.css

38 ms

frontend-legacy.min.css

frontend-legacy.min.css

33 ms

frontend.min.css

frontend.min.css

33 ms

swiper.min.css

swiper.min.css

44 ms

post-7491.css

post-7491.css

42 ms

all.min.css

all.min.css

39 ms

v4-shims.min.css

v4-shims.min.css

42 ms

post-189.css

post-189.css

41 ms

frontend.css

frontend.css

45 ms

post-7984.css

post-7984.css

48 ms

all.css

all.css

67 ms

font-awesome.min.css

font-awesome.min.css

47 ms

app.css

app.css

49 ms

style.css

style.css

47 ms

v4-shims.css

v4-shims.css

92 ms

css

css

65 ms

fontawesome.min.css

fontawesome.min.css

60 ms

solid.min.css

solid.min.css

60 ms

regular.min.css

regular.min.css

60 ms

frontend-gtag.min.js

frontend-gtag.min.js

60 ms

v4-shims.min.js

v4-shims.min.js

63 ms

jquery.min.js

jquery.min.js

63 ms

jquery-migrate.min.js

jquery-migrate.min.js

62 ms

bootstrap-modal.css

bootstrap-modal.css

80 ms

animations.min.css

animations.min.css

80 ms

waypoints.min.js

waypoints.min.js

80 ms

frontend.js

frontend.js

94 ms

themo-foot.js

themo-foot.js

93 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

94 ms

vendor_footer.js

vendor_footer.js

202 ms

main.js

main.js

200 ms

bootstrap-modal.min.js

bootstrap-modal.min.js

201 ms

jquery-numerator.min.js

jquery-numerator.min.js

200 ms

frm.min.js

frm.min.js

212 ms

api.js

api.js

298 ms

frmbtsp.js

frmbtsp.js

201 ms

webpack.runtime.min.js

webpack.runtime.min.js

217 ms

frontend-modules.min.js

frontend-modules.min.js

211 ms

core.min.js

core.min.js

219 ms

swiper.min.js

swiper.min.js

219 ms

share-link.min.js

share-link.min.js

219 ms

dialog.min.js

dialog.min.js

242 ms

frontend.min.js

frontend.min.js

255 ms

preloaded-modules.min.js

preloaded-modules.min.js

253 ms

underscore.min.js

underscore.min.js

253 ms

wp-util.min.js

wp-util.min.js

241 ms

frontend.min.js

frontend.min.js

257 ms

screenshots.png

screenshots.png

932 ms

Crypto-slide2.jpg

Crypto-slide2.jpg

195 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

60 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff

405 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff

325 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff

349 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff

348 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

97 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

98 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

133 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

148 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

145 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

82 ms

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

383 ms

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

417 ms

S6u9w4BMUTPHh7USSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh7USSwaPHw3q5d0N7w.woff

653 ms

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

638 ms

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

687 ms

fa-solid-900.woff

fa-solid-900.woff

416 ms

fa-solid-900.ttf

fa-solid-900.ttf

80 ms

fa-regular-400.woff

fa-regular-400.woff

720 ms

fa-regular-400.ttf

fa-regular-400.ttf

81 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

182 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

182 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

182 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

184 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

182 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

184 ms

eicons.woff

eicons.woff

871 ms

fa-brands-400.ttf

fa-brands-400.ttf

94 ms

recaptcha__en.js

recaptcha__en.js

114 ms

logo23w-2Artboard-1-q5v9zqpe68uqu4gff8n5igu5vks83r8v0jrysp222o.png

logo23w-2Artboard-1-q5v9zqpe68uqu4gff8n5igu5vks83r8v0jrysp222o.png

573 ms

Accessibility Review

swiftcase.co.uk accessibility score

84

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

High

[aria-hidden="true"] elements contain focusable descendents

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

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

Links do not have a discernible name

Best Practices

swiftcase.co.uk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

swiftcase.co.uk SEO score

86

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

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 Swiftcase.co.uk 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 Swiftcase.co.uk 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

swiftcase.co.uk

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