Access h2-whoa.com. H2-WHOA Lake Pleasant

name

value

score

weighting

FCP (First Contentful Paint)

Value12.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value30.4 s

0/100

25%

SI (Speed Index)

Value26.3 s

0/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value31.0 s

0/100

10%

h2-whoa.com

1653 ms

layerslider.css

42 ms

style.min.css

63 ms

be.css

81 ms

animations.min.css

55 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 65% of them (68 requests) were addressed to the original H2-whoa.com, 28% (29 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain H2-whoa.com.

Content Size

7.1 MB

After Optimization

3.5 MB

In fact, the total size of H2-whoa.com main page is 7.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 135.1 kB

Original 165.9 kB
After minification 162.6 kB
After compression 30.9 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 135.1 kB or 81% of the original size.

Image Optimization

-29%

Potential reduce by 1.2 MB

Original 3.9 MB
After minification 2.8 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. Obviously, H2 WHOA needs image optimization as it can save up to 1.2 MB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 1.4 MB

Original 1.9 MB
After minification 1.9 MB
After compression 539.7 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 1.4 MB or 72% of the original size.

CSS Optimization

-84%

Potential reduce by 886.6 kB

Original 1.1 MB
After minification 1.0 MB
After compression 165.0 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. H2-whoa.com needs all CSS files to be minified and compressed as it can save up to 886.6 kB or 84% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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

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 H2-whoa.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 H2-whoa.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

h2-whoa.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

H2-WHOA Lake Pleasant | Floating Waterslide

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

h2-whoa.com

layerslider.css

style.min.css

be.css

animations.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

h2-whoa.com

layerslider.css

style.min.css

be.css

animations.min.css

fontawesome.css

jplayer.blue.monday.min.css

responsive.css

css

css

elementor-icons.min.css

frontend-lite.min.css

swiper.min.css

post-236.css

all.min.css

v4-shims.min.css

post-83.css

style.css

css

fontawesome.min.css

solid.min.css

jquery.min.js

jquery-migrate.min.js

layerslider.utils.js

layerslider.kreaturamedia.jquery.js

layerslider.transitions.js

v4-shims.min.js

fbevents.js

h2-whoa.png

dummy.png

h2-whoa.jpg

h2-whoa-banner-2.jpg

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf