Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

grandcanyon.org

Grand Canyon Conservancy | Grand Canyon Conservancy: National Park…

Page Load Speed

1.9 sec in total

First Response

96 ms

Resources Loaded

1.5 sec

Page Rendered

247 ms

grandcanyon.org screenshot

About Website

Visit grandcanyon.org now to see the best up-to-date Grand Canyon content for United States and also check out these interesting facts you probably never knew about grandcanyon.org

Interested in learning about how to experience and protect the Grand Canyon? If so, click to discover the work GCC does and how you can get involved.

Visit grandcanyon.org

Key Findings

We analyzed Grandcanyon.org page load time and found that the first response time was 96 ms and then it took 1.8 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

grandcanyon.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value32.0 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value3,000 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value25.6 s

0/100

10%

Network Requests Diagram

grandcanyon.org

96 ms

www.grandcanyon.org

772 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

94 ms

css_wIbKzQ8qDeLhRCJKJLL_nmFtylFfHk3WD-2u5U9s5Q8.css

90 ms

css_2SK87aPPMztyKC8bAUC2WgeNxWEGrOrr_Dori4iJlLE.css

96 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 88% of them (44 requests) were addressed to the original Grandcanyon.org, 6% (3 requests) were made to S7.addthis.com and 4% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (772 ms) belongs to the original domain Grandcanyon.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (49%)

Content Size

2.4 MB

After Optimization

1.2 MB

In fact, the total size of Grandcanyon.org main page is 2.4 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. 50% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 152.1 kB

  • Original 194.3 kB
  • After minification 192.3 kB
  • After compression 42.1 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 152.1 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 22.9 kB

  • Original 857.6 kB
  • After minification 834.7 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. Grand Canyon images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 846.4 kB

  • Original 1.1 MB
  • After minification 969.2 kB
  • After compression 302.6 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 846.4 kB or 74% of the original size.

CSS Optimization

-82%

Potential reduce by 131.7 kB

  • Original 161.2 kB
  • After minification 156.1 kB
  • After compression 29.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. Grandcanyon.org needs all CSS files to be minified and compressed as it can save up to 131.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (31%)

Requests Now

48

After Optimization

33

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

Accessibility Review

grandcanyon.org accessibility score

75

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

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

grandcanyon.org best practices score

83

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

Page has valid source maps

SEO Factors

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

Links do not have descriptive text

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 Grandcanyon.org 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 Grandcanyon.org 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 description is not detected on the main page of Grand Canyon. 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: