Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

fringefestival.org

Minnesota Fringe

Page Load Speed

1.2 sec in total

First Response

102 ms

Resources Loaded

887 ms

Page Rendered

247 ms

fringefestival.org screenshot

About Website

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

Minnesota Fringe :: August 4 - August 14

Visit fringefestival.org

Key Findings

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

Performance Metrics

fringefestival.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value21.7 s

0/100

25%

SI (Speed Index)

Value18.8 s

0/100

10%

TBT (Total Blocking Time)

Value23,700 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value32.6 s

0/100

10%

Network Requests Diagram

fringefestival.org

102 ms

www.fringefestival.org

214 ms

foundation.php

310 ms

foundation-icons.css

126 ms

gibson.css

67 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 87% of them (46 requests) were addressed to the original Fringefestival.org, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (328 ms) belongs to the original domain Fringefestival.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 541.9 kB (67%)

Content Size

814.5 kB

After Optimization

272.6 kB

In fact, the total size of Fringefestival.org main page is 814.5 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. 35% of websites need less resources to load. Javascripts take 454.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 16.9 kB

  • Original 22.9 kB
  • After minification 20.1 kB
  • After compression 6.0 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. This page needs HTML code to be minified as it can gain 2.8 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 16.9 kB or 74% of the original size.

Image Optimization

-50%

Potential reduce by 138.7 kB

  • Original 279.8 kB
  • After minification 141.1 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. Obviously, Fringe Festival needs image optimization as it can save up to 138.7 kB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 341.2 kB

  • Original 454.9 kB
  • After minification 379.9 kB
  • After compression 113.7 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 341.2 kB or 75% of the original size.

CSS Optimization

-79%

Potential reduce by 45.0 kB

  • Original 56.9 kB
  • After minification 49.8 kB
  • After compression 11.9 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. Fringefestival.org needs all CSS files to be minified and compressed as it can save up to 45.0 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (35%)

Requests Now

51

After Optimization

33

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

Accessibility Review

fringefestival.org accessibility score

82

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

fringefestival.org SEO score

69

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

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 Fringefestival.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 Fringefestival.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 Fringe Festival. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: