Tools & Wizards About Us
statworkup.com screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

statworkup.com

STATworkUP DDx Clinical Guide Medical Differential Diagnosis Decision App: iOS iPhone, iPad, Android

Page Load Speed

6 sec in total

First Response

1.2 sec

Resources Loaded

4.5 sec

Page Rendered

362 ms

statworkup.com screenshot

About Website

Click here to check amazing STATworkUP content. Otherwise, check out these important facts you probably never knew about statworkup.com

STATworkUP DDx Clinical Guide | Best Problem-Oriented Medical App | iPhone Differential Diagnosis & Clinical Decision Support | iOS, iPad & Android | Correlates Symptom Diagnostics, Lab & Treatment

Visit statworkup.com

Key Findings

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

Performance Metrics

statworkup.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

3/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.653

8/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

statworkup.com

1219 ms

statworkup.com

1388 ms

js

49 ms

jquery.js

196 ms

button.css

120 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 23% of them (18 requests) were addressed to the original Statworkup.com, 43% (34 requests) were made to Assets.myregisteredsite.com and 13% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Statworkup.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 547.7 kB (33%)

Content Size

1.7 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Statworkup.com main page is 1.7 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. 60% of websites need less resources to load. Images take 875.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 91.9 kB

  • Original 116.6 kB
  • After minification 115.9 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. 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 91.9 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 93.3 kB

  • Original 875.1 kB
  • After minification 781.8 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, STATworkUP needs image optimization as it can save up to 93.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-7%

Potential reduce by 18.2 kB

  • Original 262.8 kB
  • After minification 261.6 kB
  • After compression 244.6 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

-84%

Potential reduce by 344.3 kB

  • Original 411.2 kB
  • After minification 410.4 kB
  • After compression 66.9 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. Statworkup.com needs all CSS files to be minified and compressed as it can save up to 344.3 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

67

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

statworkup.com

statworkup.com

1219 ms

statworkup.com

statworkup.com

1388 ms

js

js

49 ms

jquery.js

jquery.js

196 ms

button.css

button.css

120 ms

browserBehavior.js

browserBehavior.js

75 ms

utils.js

utils.js

153 ms

shared.js

shared.js

122 ms

navigation.js

navigation.js

222 ms

uaDefaultStylesReset.css

uaDefaultStylesReset.css

122 ms

popup.js

popup.js

296 ms

ResourceLoader.js

ResourceLoader.js

123 ms

webcom_copyright_kw.js

webcom_copyright_kw.js

124 ms

googleFonts.css

googleFonts.css

17 ms

css

css

37 ms

navigation.js

navigation.js

18 ms

core.js

core.js

20 ms

socialmediashare.js

socialmediashare.js

19 ms

footercontact.js

footercontact.js

20 ms

jqueryvalidate.js

jqueryvalidate.js

26 ms

form.js

form.js

19 ms

hoverIntent.js

hoverIntent.js

17 ms

bgIframe.js

bgIframe.js

18 ms

superfish.js

superfish.js

17 ms

handler.js

handler.js

20 ms

helper.js

helper.js

18 ms

positioner.js

positioner.js

19 ms

structure.css

structure.css

32 ms

smstemplates.js

smstemplates.js

33 ms

socialmediashare.css

socialmediashare.css

34 ms

jquery.json-2.2.min.js

jquery.json-2.2.min.js

35 ms

templates.js

templates.js

36 ms

footercontact.css

footercontact.css

35 ms

utils.js

utils.js

48 ms

resources.js

resources.js

49 ms

templates.js

templates.js

52 ms

form.css

form.css

51 ms

form_generic.css

form_generic.css

52 ms

129330918.png

129330918.png

179 ms

129320569.png

129320569.png

441 ms

129320570.png

129320570.png

572 ms

133815930.png

133815930.png

611 ms

129580757.png

129580757.png

723 ms

129580754.png

129580754.png

817 ms

133815795.png

133815795.png

888 ms

129335153.png

129335153.png

1103 ms

129845062.png

129845062.png

1178 ms

129741297.png

129741297.png

1217 ms

136253976.png

136253976.png

1224 ms

Axby_fLy8ps

Axby_fLy8ps

166 ms

_PhynbCAAd8

_PhynbCAAd8

475 ms

129321439.png

129321439.png

426 ms

129322655.jpg

129322655.jpg

1422 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

94 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

115 ms

jizaRExUiTo99u79D0KEwA.ttf

jizaRExUiTo99u79D0KEwA.ttf

90 ms

jizfRExUiTo99u79B_mh0O6tKA.ttf

jizfRExUiTo99u79B_mh0O6tKA.ttf

88 ms

jizYRExUiTo99u79D0e0x8mN.ttf

jizYRExUiTo99u79D0e0x8mN.ttf

89 ms

jizdRExUiTo99u79D0e8fOydLxUY.ttf

jizdRExUiTo99u79D0e8fOydLxUY.ttf

87 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

86 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

88 ms

placeholder.png

placeholder.png

47 ms

facebook-color.png

facebook-color.png

46 ms

twitter-color.png

twitter-color.png

46 ms

linkedin-color.png

linkedin-color.png

45 ms

www-player.css

www-player.css

15 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

55 ms

logger.php

logger.php

342 ms

ad_status.js

ad_status.js

261 ms

FaW0q-y8JjmoU9T0UDvbGph-S7KEa5MvRd-6bYW3ujg.js

FaW0q-y8JjmoU9T0UDvbGph-S7KEa5MvRd-6bYW3ujg.js

217 ms

embed.js

embed.js

136 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

41 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

41 ms

Create

Create

106 ms

Create

Create

108 ms

id

id

87 ms

GenerateIT

GenerateIT

25 ms

GenerateIT

GenerateIT

30 ms

Accessibility Review

statworkup.com accessibility score

86

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

statworkup.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

statworkup.com SEO score

96

Search Engine Optimization Advices

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

statworkup.com

Open Graph description is not detected on the main page of STATworkUP. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: