Tools & Wizards About Us
visicase.com screenshot

Report Summary

  • 38

    Performance

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

  • 91

    SEO

    Google-friendlier than
    70% of websites

visicase.com

Home - Visicase

Page Load Speed

14.1 sec in total

First Response

436 ms

Resources Loaded

13 sec

Page Rendered

740 ms

visicase.com screenshot

About Website

Welcome to visicase.com homepage info - get ready to check Visicase best content for Australia right away, or after learning these important things about visicase.com

If you were happy with ‘Just OK’, you probably wouldn’t be here. VisiCase is a leading Care Management System for NDIS and Aged Care providers across Australia. Contact Us About Us At VisiCase, we bel...

Visit visicase.com

Key Findings

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

Performance Metrics

visicase.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

visicase.com

436 ms

visicase.com

7300 ms

js

69 ms

main.min.css

432 ms

frontend.css

659 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 75% of them (101 requests) were addressed to the original Visicase.com, 20% (27 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (7.3 sec) belongs to the original domain Visicase.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 337.9 kB (6%)

Content Size

5.6 MB

After Optimization

5.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Visicase.com main page is 5.6 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. 70% of websites need less resources to load. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 210.2 kB

  • Original 255.5 kB
  • After minification 251.1 kB
  • After compression 45.2 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 210.2 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 119.5 kB

  • Original 4.9 MB
  • After minification 4.8 MB

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. Visicase images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.5 kB

  • Original 282.5 kB
  • After minification 282.5 kB
  • After compression 279.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

-3%

Potential reduce by 4.7 kB

  • Original 150.4 kB
  • After minification 150.3 kB
  • After compression 145.7 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. Visicase.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 85 (81%)

Requests Now

105

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

visicase.com

visicase.com

436 ms

visicase.com

visicase.com

7300 ms

js

js

69 ms

main.min.css

main.min.css

432 ms

frontend.css

frontend.css

659 ms

styles.css

styles.css

653 ms

contact-form-7-main.min.css

contact-form-7-main.min.css

655 ms

scroll-top.css

scroll-top.css

657 ms

buttons.min.css

buttons.min.css

663 ms

dashicons.min.css

dashicons.min.css

886 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

868 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

870 ms

media-views.min.css

media-views.min.css

876 ms

imgareaselect.css

imgareaselect.css

874 ms

uacf7-frontend.css

uacf7-frontend.css

879 ms

form-style.css

form-style.css

1084 ms

columns.css

columns.css

1087 ms

multistep.css

multistep.css

1091 ms

star-rating.css

star-rating.css

1090 ms

all.css

all.css

1100 ms

jquery-ui.css

jquery-ui.css

24 ms

style.css

style.css

1103 ms

countrySelect.min.css

countrySelect.min.css

1302 ms

style.css

style.css

1306 ms

header-footer-elementor.css

header-footer-elementor.css

1309 ms

elementor-icons.min.css

elementor-icons.min.css

1307 ms

frontend-lite.min.css

frontend-lite.min.css

1321 ms

swiper.min.css

swiper.min.css

1328 ms

post-7.css

post-7.css

1518 ms

main.css

main.css

1522 ms

global.css

global.css

1523 ms

post-179.css

post-179.css

1527 ms

post-163.css

post-163.css

1536 ms

post-195.css

post-195.css

1537 ms

style.css

style.css

1734 ms

css

css

46 ms

fontawesome.min.css

fontawesome.min.css

1741 ms

solid.min.css

solid.min.css

1739 ms

regular.min.css

regular.min.css

1746 ms

frontend-gtag.min.js

frontend-gtag.min.js

1756 ms

jquery-ui.min.js

jquery-ui.min.js

34 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

49 ms

jquery.min.js

jquery.min.js

1560 ms

jquery-migrate.min.js

jquery-migrate.min.js

1524 ms

workflow.bundle.js

workflow.bundle.js

1308 ms

utils.min.js

utils.min.js

1304 ms

moxie.min.js

moxie.min.js

1528 ms

plupload.min.js

plupload.min.js

1315 ms

frontend.min.js

frontend.min.js

1326 ms

hooks.min.js

hooks.min.js

1304 ms

i18n.min.js

i18n.min.js

1305 ms

index.js

index.js

1302 ms

index.js

index.js

1432 ms

jquery.scrollUp.min.js

jquery.scrollUp.min.js

1432 ms

underscore.min.js

underscore.min.js

1507 ms

shortcode.min.js

shortcode.min.js

1313 ms

backbone.min.js

backbone.min.js

1311 ms

wp-util.min.js

wp-util.min.js

1335 ms

wp-backbone.min.js

wp-backbone.min.js

1335 ms

media-models.min.js

media-models.min.js

1325 ms

wp-plupload.min.js

wp-plupload.min.js

1504 ms

core.min.js

core.min.js

1308 ms

mouse.min.js

mouse.min.js

1303 ms

sortable.min.js

sortable.min.js

1308 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1323 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

1326 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

1493 ms

api-request.min.js

api-request.min.js

1307 ms

dom-ready.min.js

dom-ready.min.js

1303 ms

a11y.min.js

a11y.min.js

1308 ms

clipboard.min.js

clipboard.min.js

1318 ms

media-views.min.js

media-views.min.js

1325 ms

media-editor.min.js

media-editor.min.js

1502 ms

media-audiovideo.min.js

media-audiovideo.min.js

1307 ms

redirect.js

redirect.js

1302 ms

uacf7-cf-script.js

uacf7-cf-script.js

1301 ms

multistep.js

multistep.js

1309 ms

progressbar.js

progressbar.js

1319 ms

range-slider.js

range-slider.js

1481 ms

countrySelect.js

countrySelect.js

1307 ms

script.js

script.js

1303 ms

pre-populate.js

pre-populate.js

1307 ms

scripts.js

scripts.js

1312 ms

frontend.js

frontend.js

1312 ms

webpack.runtime.min.js

webpack.runtime.min.js

1303 ms

frontend-modules.min.js

frontend-modules.min.js

1305 ms

waypoints.min.js

waypoints.min.js

1305 ms

gtm.js

gtm.js

112 ms

frontend.min.js

frontend.min.js

1176 ms

logo.png

logo.png

1194 ms

home_page_1_ps_png.png

home_page_1_ps_png.png

2059 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

25 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

32 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

35 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

33 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

33 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

32 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

34 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

35 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

35 ms

-W_8XJnvUD7dzB2Ck_kIaWMr.ttf

-W_8XJnvUD7dzB2Ck_kIaWMr.ttf

36 ms

-W__XJnvUD7dzB2KYNoY.ttf

-W__XJnvUD7dzB2KYNoY.ttf

65 ms

-W_8XJnvUD7dzB2Cy_gIaWMr.ttf

-W_8XJnvUD7dzB2Cy_gIaWMr.ttf

64 ms

-W_8XJnvUD7dzB2Cr_sIaWMr.ttf

-W_8XJnvUD7dzB2Cr_sIaWMr.ttf

62 ms

-W_9XJnvUD7dzB2CA-ofTkM.ttf

-W_9XJnvUD7dzB2CA-ofTkM.ttf

64 ms

-W_8XJnvUD7dzB2Cv_4IaWMr.ttf

-W_8XJnvUD7dzB2Cv_4IaWMr.ttf

65 ms

-W_8XJnvUD7dzB2C2_8IaWMr.ttf

-W_8XJnvUD7dzB2C2_8IaWMr.ttf

68 ms

-W_8XJnvUD7dzB2Cx_wIaWMr.ttf

-W_8XJnvUD7dzB2Cx_wIaWMr.ttf

65 ms

-W_8XJnvUD7dzB2C4_0IaWMr.ttf

-W_8XJnvUD7dzB2C4_0IaWMr.ttf

68 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJQ.ttf

67 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4VrMDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4VrMDrMfJQ.ttf

65 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDrMfJQ.ttf

67 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejMDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejMDrMfJQ.ttf

68 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNDrMfJQ.ttf

68 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4bbLDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4bbLDrMfJQ.ttf

68 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDrMfJQ.ttf

68 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejLDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejLDrMfJQ.ttf

69 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLDrMfJQ.ttf

69 ms

image-23_new-1024x683.png

image-23_new-1024x683.png

1296 ms

imgpsh_fullsize_animmew.png

imgpsh_fullsize_animmew.png

2154 ms

image-2.png

image-2.png

2127 ms

arrow02.png

arrow02.png

1275 ms

pexels-eren-li-7188737-1024x683.jpg

pexels-eren-li-7188737-1024x683.jpg

1717 ms

icon-4.png

icon-4.png

1480 ms

image-34.png

image-34.png

1311 ms

image-21.png

image-21.png

2376 ms

imgpsh_fullsize_anim211.png

imgpsh_fullsize_anim211.png

1522 ms

imgpsh_fullsize_anim111.png

imgpsh_fullsize_anim111.png

1737 ms

Untitled-17-1.png

Untitled-17-1.png

1923 ms

Untitled-2-1.png

Untitled-2-1.png

2771 ms

imgpsh_fullsize_anim1.png

imgpsh_fullsize_anim1.png

1764 ms

new.png

new.png

1960 ms

Untitled-1-2.png

Untitled-1-2.png

2181 ms

blue-logo.png

blue-logo.png

1960 ms

Accessibility Review

visicase.com accessibility score

90

Accessibility Issues

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

visicase.com SEO score

91

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Visicase.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 Visicase.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

visicase.com

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