Tools & Wizards About Us
graeae.org screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    53% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

graeae.org

Graeae | world-class theatre & training from D/deaf & disabled artists

Page Load Speed

3.6 sec in total

First Response

967 ms

Resources Loaded

1.9 sec

Page Rendered

698 ms

graeae.org screenshot

About Website

Click here to check amazing Graeae content for United Kingdom. Otherwise, check out these important facts you probably never knew about graeae.org

Graeae Theatre Company. Productions across the UK, creative learning & training opportunities & rehearsal space hire at award-winning Bradbury Studios.

Visit graeae.org

Key Findings

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

Performance Metrics

graeae.org performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value3,870 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

graeae.org

967 ms

gtm.js

70 ms

style.min.css

100 ms

style.css

278 ms

graeae-40th-logo@2x.png

289 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 59% of them (22 requests) were addressed to the original Graeae.org, 5% (2 requests) were made to Google-analytics.com and 5% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (967 ms) belongs to the original domain Graeae.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.4 kB (7%)

Content Size

671.3 kB

After Optimization

623.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Graeae.org main page is 671.3 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. 55% of websites need less resources to load. Images take 503.4 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 35.7 kB

  • Original 48.7 kB
  • After minification 48.7 kB
  • After compression 13.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. 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 35.7 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 6.8 kB

  • Original 503.4 kB
  • After minification 496.6 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. Graeae images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.4 kB

  • Original 77.7 kB
  • After minification 77.7 kB
  • After compression 76.3 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

-8%

Potential reduce by 3.5 kB

  • Original 41.5 kB
  • After minification 41.5 kB
  • After compression 38.0 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. Graeae.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (45%)

Requests Now

31

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

graeae.org

graeae.org

967 ms

gtm.js

gtm.js

70 ms

style.min.css

style.min.css

100 ms

style.css

style.css

278 ms

graeae-40th-logo@2x.png

graeae-40th-logo@2x.png

289 ms

graeae-40th-logo-white@2x.png

graeae-40th-logo-white@2x.png

274 ms

jquery.min.js

jquery.min.js

32 ms

combined.all.min.js

combined.all.min.js

367 ms

froogaloop2.min.js

froogaloop2.min.js

59 ms

custom.js

custom.js

250 ms

conversion.js

conversion.js

30 ms

Showreel-image10-1401x758.jpg

Showreel-image10-1401x758.jpg

451 ms

The-House-of-Bernada-Alba-3-851x568.jpg

The-House-of-Bernada-Alba-3-851x568.jpg

360 ms

woven-o-web-851x568.jpg

woven-o-web-851x568.jpg

737 ms

6F7A1919-web-851x568.jpg

6F7A1919-web-851x568.jpg

379 ms

IMG_2495-851x568.jpg

IMG_2495-851x568.jpg

386 ms

Podcast-logo-450x450.png

Podcast-logo-450x450.png

736 ms

ACE_logo.png

ACE_logo.png

452 ms

ACE_logo_invert.png

ACE_logo_invert.png

735 ms

analytics.js

analytics.js

99 ms

fbevents.js

fbevents.js

57 ms

164 ms

1576673829019442

1576673829019442

97 ms

collect

collect

54 ms

fontello.css

fontello.css

208 ms

57 ms

collect

collect

58 ms

footer-slice.png

footer-slice.png

191 ms

WorkSans-Medium.woff

WorkSans-Medium.woff

195 ms

WorkSans-Bold.woff

WorkSans-Bold.woff

161 ms

fontello.woff

fontello.woff

94 ms

Neuton-Regular.woff

Neuton-Regular.woff

175 ms

Neuton-Bold.woff

Neuton-Bold.woff

93 ms

cookieconsent.min.js

cookieconsent.min.js

31 ms

71 ms

21 ms

dark-bottom.css

dark-bottom.css

16 ms

Accessibility Review

graeae.org accessibility score

84

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

High

Some elements have a [tabindex] value greater than 0

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

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

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

graeae.org SEO score

84

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

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

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

graeae.org

Open Graph data is detected on the main page of Graeae. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: