Tools & Wizards About Us
piiers.org screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

piiers.org

PIIERS | Personal Injury, Illness, and Exposure Reporting System

Page Load Speed

1.9 sec in total

First Response

390 ms

Resources Loaded

1.4 sec

Page Rendered

125 ms

piiers.org screenshot

About Website

Click here to check amazing PIIERS content. Otherwise, check out these important facts you probably never knew about piiers.org

PIIERS - Personal Internet Injury Exposure and Reporting System

Visit piiers.org

Key Findings

We analyzed Piiers.org page load time and found that the first response time was 390 ms and then it took 1.6 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

piiers.org performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value5.4 s

71/100

10%

Network Requests Diagram

www.piiers.org

390 ms

tundra.css

53 ms

site2f.css

178 ms

css

41 ms

jquery.min.js

56 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 7% of them (9 requests) were addressed to the original Piiers.org, 87% (109 requests) were made to Ajax.googleapis.com and 2% (2 requests) were made to Server6.unionactive.com. The less responsive or slowest element that took the longest time to load (568 ms) relates to the external source Server6.unionactive.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 127.3 kB (21%)

Content Size

610.7 kB

After Optimization

483.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Piiers.org main page is 610.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 324.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 25.2 kB

  • Original 30.0 kB
  • After minification 27.5 kB
  • After compression 4.8 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 25.2 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 14.9 kB

  • Original 324.8 kB
  • After minification 309.9 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. PIIERS images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 55.1 kB

  • Original 220.4 kB
  • After minification 208.9 kB
  • After compression 165.3 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 55.1 kB or 25% of the original size.

CSS Optimization

-90%

Potential reduce by 32.1 kB

  • Original 35.5 kB
  • After minification 26.6 kB
  • After compression 3.4 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. Piiers.org needs all CSS files to be minified and compressed as it can save up to 32.1 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 108 (89%)

Requests Now

121

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.piiers.org

www.piiers.org

390 ms

tundra.css

tundra.css

53 ms

site2f.css

site2f.css

178 ms

css

css

41 ms

jquery.min.js

jquery.min.js

56 ms

dojo.js

dojo.js

62 ms

site.js

site.js

266 ms

TooltipDialog.js

TooltipDialog.js

46 ms

DropDownButton.js

DropDownButton.js

44 ms

ContentPane.js

ContentPane.js

58 ms

ContentPane.js

ContentPane.js

57 ms

TabContainer.js

TabContainer.js

57 ms

scroll.js

scroll.js

58 ms

parser.js

parser.js

57 ms

easing.js

easing.js

56 ms

Dialog.js

Dialog.js

65 ms

iframe.js

iframe.js

65 ms

171625235

171625235

306 ms

apple_app_store.png

apple_app_store.png

507 ms

google_app_store.png

google_app_store.png

568 ms

wscff-piiers%20logoV1.png

wscff-piiers%20logoV1.png

149 ms

spacer.png

spacer.png

119 ms

lock-small.png

lock-small.png

188 ms

UA_Logo2.png

UA_Logo2.png

244 ms

footer_anchor.png

footer_anchor.png

260 ms

Bill%20Hoover.jpg

Bill%20Hoover.jpg

537 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

35 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

43 ms

registry.js

registry.js

22 ms

popup.js

popup.js

17 ms

Button.js

Button.js

18 ms

_Container.js

_Container.js

17 ms

_HasDropDown.js

_HasDropDown.js

29 ms

a11yclick.js

a11yclick.js

27 ms

focus.js

focus.js

33 ms

_DialogMixin.js

_DialogMixin.js

25 ms

_FormMixin.js

_FormMixin.js

24 ms

_TemplatedMixin.js

_TemplatedMixin.js

25 ms

main.js

main.js

31 ms

_Widget.js

_Widget.js

28 ms

_ContentPaneResizeMixin.js

_ContentPaneResizeMixin.js

27 ms

string.js

string.js

25 ms

html.js

html.js

28 ms

loading.js

loading.js

32 ms

_base.js

_base.js

30 ms

_TabContainerBase.js

_TabContainerBase.js

31 ms

TabController.js

TabController.js

30 ms

ScrollingTabController.js

ScrollingTabController.js

32 ms

url.js

url.js

30 ms

all.js

all.js

31 ms

stamp.js

stamp.js

32 ms

_base.js

_base.js

32 ms

_core.js

_core.js

31 ms

place.js

place.js

29 ms

BackgroundIframe.js

BackgroundIframe.js

28 ms

Viewport.js

Viewport.js

37 ms

touch.js

touch.js

38 ms

_FormWidget.js

_FormWidget.js

38 ms

_ButtonMixin.js

_ButtonMixin.js

39 ms

main.js

main.js

37 ms

Dialog.js

Dialog.js

38 ms

window.js

window.js

38 ms

fx.js

fx.js

40 ms

DialogSimple.js

DialogSimple.js

39 ms

iframe.js

iframe.js

88 ms

cache.js

cache.js

29 ms

_AttachMixin.js

_AttachMixin.js

28 ms

_FocusMixin.js

_FocusMixin.js

29 ms

a11y.js

a11y.js

29 ms

Stateful.js

Stateful.js

24 ms

utils.js

utils.js

25 ms

_WidgetBase.js

_WidgetBase.js

24 ms

_OnDijitClickMixin.js

_OnDijitClickMixin.js

38 ms

uacss.js

uacss.js

38 ms

hccss.js

hccss.js

39 ms

StackController.js

StackController.js

31 ms

Menu.js

Menu.js

31 ms

MenuItem.js

MenuItem.js

33 ms

common.js

common.js

33 ms

StackContainer.js

StackContainer.js

33 ms

_WidgetsInTemplateMixin.js

_WidgetsInTemplateMixin.js

32 ms

fx.js

fx.js

32 ms

_CssStateMixin.js

_CssStateMixin.js

20 ms

_FormWidgetMixin.js

_FormWidgetMixin.js

19 ms

Moveable.js

Moveable.js

19 ms

TimedMoveable.js

TimedMoveable.js

19 ms

manager.js

manager.js

19 ms

DialogUnderlay.js

DialogUnderlay.js

19 ms

Destroyable.js

Destroyable.js

21 ms

hccss.js

hccss.js

9 ms

ToggleButton.js

ToggleButton.js

9 ms

DropDownMenu.js

DropDownMenu.js

8 ms

_Contained.js

_Contained.js

8 ms

cookie.js

cookie.js

15 ms

_LayoutWidget.js

_LayoutWidget.js

15 ms

common.js

common.js

15 ms

Mover.js

Mover.js

14 ms

_ToggleButtonMixin.js

_ToggleButtonMixin.js

9 ms

_MenuBase.js

_MenuBase.js

8 ms

blank.gif

blank.gif

8 ms

NodeList-manipulate.js

NodeList-manipulate.js

6 ms

regexp.js

regexp.js

6 ms

autoscroll.js

autoscroll.js

6 ms

_KeyNavContainer.js

_KeyNavContainer.js

6 ms

_KeyNavMixin.js

_KeyNavMixin.js

5 ms

Toggler.js

Toggler.js

5 ms

_base.js

_base.js

15 ms

WidgetSet.js

WidgetSet.js

6 ms

focus.js

focus.js

4 ms

place.js

place.js

6 ms

popup.js

popup.js

9 ms

scroll.js

scroll.js

7 ms

sniff.js

sniff.js

6 ms

typematic.js

typematic.js

9 ms

wai.js

wai.js

11 ms

window.js

window.js

9 ms

selection.js

selection.js

8 ms

typematic.js

typematic.js

5 ms

_FormValueWidget.js

_FormValueWidget.js

5 ms

_FormValueMixin.js

_FormValueMixin.js

6 ms

ComboButton.js

ComboButton.js

5 ms

PopupMenuItem.js

PopupMenuItem.js

8 ms

CheckedMenuItem.js

CheckedMenuItem.js

8 ms

MenuSeparator.js

MenuSeparator.js

7 ms

api.js

api.js

8 ms

Accessibility Review

piiers.org accessibility score

48

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

piiers.org 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

piiers.org SEO score

92

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Piiers.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Piiers.org 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

piiers.org

Open Graph description is not detected on the main page of PIIERS. 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: