Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

h2olab.net

Acculab Inc. ⋆ Environmental water testing laboratory

Page Load Speed

21.7 sec in total

First Response

31 ms

Resources Loaded

19.8 sec

Page Rendered

1.9 sec

h2olab.net screenshot

About Website

Visit h2olab.net now to see the best up-to-date H 2 Olab content and also check out these interesting facts you probably never knew about h2olab.net

Acculab Inc. Gives You The Quality You Expect, The Service You Deserve. Environmental water testing laboratory Logan WV

Visit h2olab.net

Key Findings

We analyzed H2olab.net page load time and found that the first response time was 31 ms and then it took 21.7 sec 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

h2olab.net performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value21.9 s

0/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.868

4/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

h2olab.net

31 ms

h2olab.net

16148 ms

wp-emoji-release.min.js

8 ms

style.min.css

52 ms

shortcodes.css

27 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to H2olab.net and no external sources were called. The less responsive or slowest element that took the longest time to load (16.1 sec) belongs to the original domain H2olab.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.4 kB (1%)

Content Size

4.8 MB

After Optimization

4.8 MB

In fact, the total size of H2olab.net main page is 4.8 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. 40% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 39.8 kB

  • Original 50.5 kB
  • After minification 49.3 kB
  • After compression 10.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 39.8 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 12.2 kB

  • Original 4.7 MB
  • After minification 4.7 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. H 2 Olab images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 2.6 kB

  • Original 48.0 kB
  • After minification 48.0 kB
  • After compression 45.4 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

-15%

Potential reduce by 3.9 kB

  • Original 25.5 kB
  • After minification 25.5 kB
  • After compression 21.6 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. H2olab.net needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (36%)

Requests Now

22

After Optimization

14

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

Accessibility Review

h2olab.net accessibility score

66

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

h2olab.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

h2olab.net SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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