Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

nationalparks.org

National Park Foundation

Page Load Speed

246.3 sec in total

First Response

398 ms

Resources Loaded

37.6 sec

Page Rendered

208.3 sec

nationalparks.org screenshot

About Website

Visit nationalparks.org now to see the best up-to-date National Park S content for United States and also check out these interesting facts you probably never knew about nationalparks.org

As the official charitable partner of the National Park Service, we provide resources for the national parks. Support this uniquely American idea.

Visit nationalparks.org

Key Findings

We analyzed Nationalparks.org page load time and found that the first response time was 398 ms and then it took 245.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

nationalparks.org performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

nationalparks.org

398 ms

www.nationalparks.org

3170 ms

gtm.js

1328 ms

aud6reu.js

1753 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

457 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 74% of them (71 requests) were addressed to the original Nationalparks.org, 10% (10 requests) were made to Use.typekit.net and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (9.5 sec) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (18%)

Content Size

18.2 MB

After Optimization

14.9 MB

In fact, the total size of Nationalparks.org main page is 18.2 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. 85% 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 16.4 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 231.3 kB

  • Original 323.4 kB
  • After minification 321.3 kB
  • After compression 92.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 231.3 kB or 72% of the original size.

Image Optimization

-13%

Potential reduce by 2.1 MB

  • Original 16.4 MB
  • After minification 14.3 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, National Park S needs image optimization as it can save up to 2.1 MB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 586.6 kB

  • Original 969.8 kB
  • After minification 969.1 kB
  • After compression 383.2 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 586.6 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 387.8 kB

  • Original 463.0 kB
  • After minification 459.3 kB
  • After compression 75.2 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. Nationalparks.org needs all CSS files to be minified and compressed as it can save up to 387.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (28%)

Requests Now

82

After Optimization

59

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

Accessibility Review

nationalparks.org accessibility score

94

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

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

nationalparks.org best practices score

75

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

SEO Factors

nationalparks.org SEO score

93

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

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

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 Nationalparks.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 Nationalparks.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 data is detected on the main page of National Park S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: