Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

falls.com

Fun At The Falls - Niagara Clifton Group

Page Load Speed

3 sec in total

First Response

188 ms

Resources Loaded

1.7 sec

Page Rendered

1.2 sec

falls.com screenshot

About Website

Visit falls.com now to see the best up-to-date Falls content for United States and also check out these interesting facts you probably never knew about falls.com

Niagara Falls Clifton Hill. Ready to have some Fun At The Falls? There is so much to do! Attractions, Accommodations, Dining and Shopping!

Visit falls.com

Key Findings

We analyzed Falls.com page load time and found that the first response time was 188 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

falls.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value30.4 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value3,640 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value32.3 s

0/100

10%

Network Requests Diagram

falls.com

188 ms

falls.com

121 ms

frontend.css

28 ms

ht-slider-widgets.css

42 ms

general.min.css

52 ms

Our browser made a total of 169 requests to load all elements on the main page. We found that 84% of them (142 requests) were addressed to the original Falls.com, 7% (11 requests) were made to Fonts.gstatic.com and 4% (7 requests) were made to Niagaraclifton.wpenginepowered.com. The less responsive or slowest element that took the longest time to load (743 ms) relates to the external source Cdn.userway.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 351.7 kB (5%)

Content Size

6.7 MB

After Optimization

6.3 MB

In fact, the total size of Falls.com main page is 6.7 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. Only a small number of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 220.2 kB

  • Original 253.6 kB
  • After minification 242.6 kB
  • After compression 33.4 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 220.2 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 120.3 kB

  • Original 6.0 MB
  • After minification 5.9 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. Falls images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.2 kB

  • Original 275.0 kB
  • After minification 275.0 kB
  • After compression 271.8 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

-5%

Potential reduce by 8.0 kB

  • Original 168.6 kB
  • After minification 168.6 kB
  • After compression 160.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. Falls.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 62 (42%)

Requests Now

147

After Optimization

85

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

Accessibility Review

falls.com accessibility score

80

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Best Practices

falls.com best practices score

67

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

falls.com SEO score

84

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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