Tools & Wizards About Us
graeae.org screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 0

    Best Practices

  • 86

    SEO

    Google-friendlier than
    60% of websites

graeae.org

Home - Graeae

Page Load Speed

5.4 sec in total

First Response

1.2 sec

Resources Loaded

3.2 sec

Page Rendered

1.1 sec

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

We create radical theatre, placing access at the heart of our work.

Visit graeae.org

Key Findings

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

Performance Metrics

graeae.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value1,860 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

graeae.org

1195 ms

iframe_api

38 ms

style.min.css

305 ms

cookie-law-info-public.css

231 ms

cookie-law-info-gdpr.css

232 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 79% of them (15 requests) were addressed to the original Graeae.org, 11% (2 requests) were made to Youtube.com and 5% (1 request) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Graeae.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.7 MB (83%)

Content Size

9.3 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Graeae.org main page is 9.3 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. 15% of websites need less resources to load. HTML takes 8.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 7.7 MB

  • Original 8.5 MB
  • After minification 5.7 MB
  • After compression 874.4 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 MB, which is 33% 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 7.7 MB or 90% of the original size.

Image Optimization

-15%

Potential reduce by 80.4 kB

  • Original 544.5 kB
  • After minification 464.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, Graeae needs image optimization as it can save up to 80.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 365 B

  • Original 193.3 kB
  • After minification 193.3 kB
  • After compression 192.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

-4%

Potential reduce by 1.9 kB

  • Original 48.5 kB
  • After minification 48.5 kB
  • After compression 46.6 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 15 (83%)

Requests Now

18

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 18 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 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

graeae.org

graeae.org

1195 ms

iframe_api

iframe_api

38 ms

style.min.css

style.min.css

305 ms

cookie-law-info-public.css

cookie-law-info-public.css

231 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

232 ms

image-renderer.css

image-renderer.css

234 ms

main.css

main.css

313 ms

script.min.js

script.min.js

383 ms

jquery.min.js

jquery.min.js

384 ms

jquery-migrate.min.js

jquery-migrate.min.js

311 ms

cookie-law-info-public.js

cookie-law-info-public.js

379 ms

a11y-dialog.min.js

a11y-dialog.min.js

15 ms

www-widgetapi.js

www-widgetapi.js

4 ms

css2

css2

33 ms

c70e5e2f29c5a4307b0afe1604a8f959.png

c70e5e2f29c5a4307b0afe1604a8f959.png

762 ms

cookie-law-info-table.css

cookie-law-info-table.css

76 ms

lazysizes.min.js

lazysizes.min.js

90 ms

jquery.wp-smartcrop.min.js

jquery.wp-smartcrop.min.js

89 ms

main.js

main.js

234 ms

Accessibility Review

graeae.org accessibility score

89

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

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.

SEO Factors

graeae.org SEO score

86

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

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: