Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 62

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

procure.ohio.gov

State of Ohio Procurement

Page Load Speed

293 ms in total

First Response

97 ms

Resources Loaded

102 ms

Page Rendered

94 ms

procure.ohio.gov screenshot

About Website

Welcome to procure.ohio.gov homepage info - get ready to check Procure Ohio best content for United States right away, or after learning these important things about procure.ohio.gov

State of Ohio Procurement state procurement term schedules master agreements

Visit procure.ohio.gov

Key Findings

We analyzed Procure.ohio.gov page load time and found that the first response time was 97 ms and then it took 196 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

procure.ohio.gov performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

3/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

procure.ohio.gov

97 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Procure.ohio.gov and no external sources were called. The less responsive or slowest element that took the longest time to load (97 ms) belongs to the original domain Procure.ohio.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 35 B (16%)

Content Size

220 B

After Optimization

185 B

In fact, the total size of Procure.ohio.gov main page is 220 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 220 B which makes up the majority of the site volume.

HTML Optimization

-16%

Potential reduce by 35 B

  • Original 220 B
  • After minification 216 B
  • After compression 185 B

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 35 B or 16% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

procure.ohio.gov accessibility score

85

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-hidden="true"] elements contain focusable descendents

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

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

Best Practices

procure.ohio.gov best practices score

62

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

procure.ohio.gov 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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Procure.ohio.gov 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 Procure.ohio.gov main page’s claimed encoding is . 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

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