Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

azwild.org

Arizona Wilderness Coalition - Protect & Restore Arizona's Wilderness

Page Load Speed

522 ms in total

First Response

43 ms

Resources Loaded

322 ms

Page Rendered

157 ms

About Website

Visit azwild.org now to see the best up-to-date Azwild content and also check out these interesting facts you probably never knew about azwild.org

An ad hoc organization of groups and individuals whose mission is to permanently protect and restore Wilderness and other wild lands and waters in Arizona

Visit azwild.org

Key Findings

We analyzed Azwild.org page load time and found that the first response time was 43 ms and then it took 479 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

azwild.org performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value25.9 s

0/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

azwild.org

43 ms

www.azwild.org

62 ms

js

99 ms

banner-rotator.css

7 ms

style.css

17 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 92% of them (69 requests) were addressed to the original Azwild.org, 3% (2 requests) were made to Ajax.googleapis.com and 3% (2 requests) were made to Assets.juicer.io. The less responsive or slowest element that took the longest time to load (99 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 238.2 kB (6%)

Content Size

3.7 MB

After Optimization

3.5 MB

In fact, the total size of Azwild.org main page is 3.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. 75% 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 53.9 kB

  • Original 63.2 kB
  • After minification 60.5 kB
  • After compression 9.3 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 53.9 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 170.8 kB

  • Original 3.4 MB
  • After minification 3.2 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. Azwild images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.5 kB

  • Original 282.9 kB
  • After minification 282.9 kB
  • After compression 281.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

-38%

Potential reduce by 12.1 kB

  • Original 31.8 kB
  • After minification 31.7 kB
  • After compression 19.7 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. Azwild.org needs all CSS files to be minified and compressed as it can save up to 12.1 kB or 38% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

50

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

Accessibility Review

azwild.org accessibility score

70

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

azwild.org best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

azwild.org SEO score

50

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Azwild.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Azwild.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Azwild. 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: