Tools & Wizards About Us
worksafe.api.org screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

worksafe.api.org

API Company Search

Page Load Speed

2 sec in total

First Response

56 ms

Resources Loaded

1.8 sec

Page Rendered

134 ms

worksafe.api.org screenshot

About Website

Visit worksafe.api.org now to see the best up-to-date Worksafe API content for United States and also check out these interesting facts you probably never knew about worksafe.api.org

Visit worksafe.api.org

Key Findings

We analyzed Worksafe.api.org page load time and found that the first response time was 56 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

worksafe.api.org performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value23.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.7 s

0/100

25%

SI (Speed Index)

Value23.7 s

0/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

worksafe.api.org

56 ms

worksafe.api.org

75 ms

jquery-1.4.1.js

1501 ms

API.css

31 ms

socialBar.css

46 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 90% of them (27 requests) were addressed to the original Worksafe.api.org, 7% (2 requests) were made to Ssl.google-analytics.com and 3% (1 request) were made to Html5shiv.googlecode.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Worksafe.api.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 202.0 kB (64%)

Content Size

314.2 kB

After Optimization

112.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worksafe.api.org main page is 314.2 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. 15% of websites need less resources to load. Javascripts take 188.4 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 9.1 kB

  • Original 13.6 kB
  • After minification 12.6 kB
  • After compression 4.5 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 9.1 kB or 67% of the original size.

Image Optimization

-37%

Potential reduce by 33.2 kB

  • Original 90.1 kB
  • After minification 56.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. Obviously, Worksafe API needs image optimization as it can save up to 33.2 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 141.1 kB

  • Original 188.4 kB
  • After minification 119.3 kB
  • After compression 47.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 141.1 kB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 18.6 kB

  • Original 22.1 kB
  • After minification 15.7 kB
  • After compression 3.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. Worksafe.api.org needs all CSS files to be minified and compressed as it can save up to 18.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (43%)

Requests Now

28

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

worksafe.api.org

worksafe.api.org

56 ms

worksafe.api.org

worksafe.api.org

75 ms

jquery-1.4.1.js

jquery-1.4.1.js

1501 ms

API.css

API.css

31 ms

socialBar.css

socialBar.css

46 ms

html5.js

html5.js

58 ms

TopAPILeft.jpg

TopAPILeft.jpg

182 ms

TopRight_Home.png

TopRight_Home.png

15 ms

TopRight_Contact.png

TopRight_Contact.png

51 ms

TopRight_Help.png

TopRight_Help.png

49 ms

worksafe-nebraska-ust.gif

worksafe-nebraska-ust.gif

69 ms

NewUser.gif

NewUser.gif

69 ms

RegisterButton.gif

RegisterButton.gif

86 ms

ExistingUsers.gif

ExistingUsers.gif

85 ms

LoginButton.gif

LoginButton.gif

67 ms

Button_RecoverPassword.gif

Button_RecoverPassword.gif

110 ms

Title_OnlineDIR.png

Title_OnlineDIR.png

109 ms

Button_OnlineDirectory.png

Button_OnlineDirectory.png

109 ms

ValidateSafetyKey.gif

ValidateSafetyKey.gif

110 ms

Button_Verify.gif

Button_Verify.gif

108 ms

Title_Available.gif

Title_Available.gif

145 ms

logo_energyCitizens.png

logo_energyCitizens.png

148 ms

logo_energyNation.png

logo_energyNation.png

149 ms

logo_energyShale.png

logo_energyShale.png

146 ms

logo_energyTomorrow.png

logo_energyTomorrow.png

144 ms

TopBack.gif

TopBack.gif

136 ms

bg_social.jpg

bg_social.jpg

128 ms

ico_social.jpg

ico_social.jpg

129 ms

ga.js

ga.js

67 ms

__utm.gif

__utm.gif

14 ms

Accessibility Review

worksafe.api.org accessibility score

82

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

Best Practices

worksafe.api.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

worksafe.api.org SEO score

83

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Worksafe.api.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Worksafe.api.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

worksafe.api.org

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