Tools & Wizards About Us
evergreenfair.org screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

evergreenfair.org

Evergreen State Fairgrounds, WA - Official Website | Official Website

Page Load Speed

1.8 sec in total

First Response

116 ms

Resources Loaded

1.5 sec

Page Rendered

170 ms

evergreenfair.org screenshot

About Website

Welcome to evergreenfair.org homepage info - get ready to check Evergreen Fair best content for United States right away, or after learning these important things about evergreenfair.org

Located in Monroe, Washington Since 1949, the 193-acre Evergreen State Fairgrounds is home to the Evergreen State Fair. The annual fair is one of the largest events held annually in the Pacific Northw...

Visit evergreenfair.org

Key Findings

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

evergreenfair.org performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value17.0 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value2,260 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.419

23/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

evergreenfair.org

116 ms

www.evergreenfair.org

492 ms

gtm.js

64 ms

gtm.js

106 ms

antiforgery

105 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 62% of them (39 requests) were addressed to the original Evergreenfair.org, 16% (10 requests) were made to Googletagmanager.com and 8% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (492 ms) belongs to the original domain Evergreenfair.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.3 kB (17%)

Content Size

562.7 kB

After Optimization

467.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Evergreenfair.org main page is 562.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 348.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 72.7 kB

  • Original 92.9 kB
  • After minification 87.0 kB
  • After compression 20.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 72.7 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 11.9 kB

  • Original 348.9 kB
  • After minification 337.0 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. Evergreen Fair images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 8.9 kB

  • Original 112.8 kB
  • After minification 112.7 kB
  • After compression 103.9 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

-23%

Potential reduce by 1.9 kB

  • Original 8.0 kB
  • After minification 8.0 kB
  • After compression 6.1 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. Evergreenfair.org needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (66%)

Requests Now

58

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

evergreenfair.org

evergreenfair.org

116 ms

www.evergreenfair.org

www.evergreenfair.org

492 ms

gtm.js

gtm.js

64 ms

gtm.js

gtm.js

106 ms

antiforgery

antiforgery

105 ms

fbevents.js

fbevents.js

30 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

167 ms

jQuery-migrate-1.4.1.js

jQuery-migrate-1.4.1.js

218 ms

-1542169068.css

-1542169068.css

368 ms

1372504222.css

1372504222.css

288 ms

248816995.js

248816995.js

382 ms

ai.0.js

ai.0.js

17 ms

jquery.ui.autocomplete.min.js

jquery.ui.autocomplete.min.js

220 ms

Search.js

Search.js

220 ms

jquery-ui.css

jquery-ui.css

296 ms

PausePlay.css

PausePlay.css

295 ms

1700977764.js

1700977764.js

294 ms

Calendar.js

Calendar.js

333 ms

jquery.urlToLink.min.js

jquery.urlToLink.min.js

335 ms

745732998.css

745732998.css

334 ms

APIClient.js

APIClient.js

334 ms

Moment.min.js

Moment.min.js

335 ms

SplashModalRender.js

SplashModalRender.js

335 ms

58870828.js

58870828.js

454 ms

js

js

96 ms

js

js

99 ms

analytics.js

analytics.js

44 ms

js

js

151 ms

collect

collect

19 ms

js

js

48 ms

Document

Document

51 ms

Document

Document

52 ms

Document

Document

51 ms

Document

Document

53 ms

Document

Document

53 ms

Document

Document

124 ms

Document

Document

123 ms

Document

Document

161 ms

Document

Document

123 ms

Document

Document

123 ms

Document

Document

162 ms

Document

Document

166 ms

Document

Document

163 ms

Document

Document

164 ms

Document

Document

167 ms

Document

Document

222 ms

Document

Document

321 ms

gtm.js

gtm.js

51 ms

Document

Document

237 ms

collect

collect

74 ms

js

js

172 ms

js

js

172 ms

collect

collect

62 ms

collect

collect

175 ms

collect

collect

134 ms

js

js

94 ms

Print.css

Print.css

110 ms

collect

collect

25 ms

generic

generic

14 ms

ga-audiences

ga-audiences

52 ms

ga-audiences

ga-audiences

70 ms

rubicon

rubicon

3 ms

appnexus

appnexus

4 ms

Accessibility Review

evergreenfair.org 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-hidden="true"] elements contain focusable descendents

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

evergreenfair.org SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

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

evergreenfair.org

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