Tools & Wizards About Us
rgs.org screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

rgs.org

Home - RGS

Page Load Speed

7 sec in total

First Response

157 ms

Resources Loaded

6.5 sec

Page Rendered

343 ms

rgs.org screenshot

About Website

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

The Royal Geographical Society (with IBG) is a learned society and professional body for geography. Explore our resources and events, and join our community.

Visit rgs.org

Key Findings

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

Performance Metrics

rgs.org performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

rgs.org

157 ms

rgs.org

356 ms

www.rgs.org

954 ms

otSDKStub.js

59 ms

js

65 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 11% of them (4 requests) were addressed to the original Rgs.org, 58% (22 requests) were made to Cdn-rgs-media-prod.azureedge.net and 11% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Cdn-rgs-media-prod.azureedge.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 277.1 kB (20%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 237.0 kB

  • Original 285.3 kB
  • After minification 284.9 kB
  • After compression 48.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 237.0 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 28.3 kB

  • Original 949.7 kB
  • After minification 921.4 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. RGS images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 11.8 kB

  • Original 165.7 kB
  • After minification 165.7 kB
  • After compression 153.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

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 6 (19%)

Requests Now

32

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rgs.org

rgs.org

157 ms

rgs.org

rgs.org

356 ms

www.rgs.org

www.rgs.org

954 ms

otSDKStub.js

otSDKStub.js

59 ms

js

js

65 ms

client-b7c132f5f3dea89af24d.js

client-b7c132f5f3dea89af24d.js

314 ms

mmq7hji.css

mmq7hji.css

94 ms

acc1c553-3ac8-41e0-b071-854e2d888c28-test.json

acc1c553-3ac8-41e0-b071-854e2d888c28-test.json

82 ms

gtm.js

gtm.js

81 ms

p.css

p.css

116 ms

location

location

125 ms

shackleton-2022-15.jpg

shackleton-2022-15.jpg

2052 ms

royal_medals_3.jpg

royal_medals_3.jpg

2544 ms

website-resources-landing-page-copyright-rgsibg.jpg

website-resources-landing-page-copyright-rgsibg.jpg

2142 ms

gfg-2014-reznichenko-kyrgyzstan_1.jpg

gfg-2014-reznichenko-kyrgyzstan_1.jpg

2112 ms

overseas-fieldwork.jpg

overseas-fieldwork.jpg

3117 ms

royal-geographical-society-stills-high-res-24.jpg

royal-geographical-society-stills-high-res-24.jpg

2115 ms

hero-carousel-example.png

hero-carousel-example.png

3035 ms

adobestock_300982397.jpg

adobestock_300982397.jpg

2665 ms

pexels-marcus-aurelius-4064170-cropped.jpg

pexels-marcus-aurelius-4064170-cropped.jpg

2638 ms

ex070524.jpg

ex070524.jpg

2722 ms

adobestock_276941222.jpeg

adobestock_276941222.jpeg

4553 ms

asa-steinarsdottir-nudz0d3ysaa-unsplash.jpg

asa-steinarsdottir-nudz0d3ysaa-unsplash.jpg

2669 ms

6_darvill_waltkund_credit_matt-tomkinsjpg.png

6_darvill_waltkund_credit_matt-tomkinsjpg.png

4024 ms

medals_1.jpg

medals_1.jpg

3473 ms

loraine-rutt_mapping-earth_porcelain-and-bog-oak_10x14x12cm_photo_sylvain-deleu.jpg

loraine-rutt_mapping-earth_porcelain-and-bog-oak_10x14x12cm_photo_sylvain-deleu.jpg

4419 ms

dsc_1178.jpg

dsc_1178.jpg

4358 ms

box_6.jpg

box_6.jpg

4103 ms

unp-rgs-32327-kensington-017-newsky.jpg

unp-rgs-32327-kensington-017-newsky.jpg

4091 ms

banwell1_1.jfif

banwell1_1.jfif

4539 ms

website-resources-landing-page-copyright-rgsibg.jpg

website-resources-landing-page-copyright-rgsibg.jpg

4979 ms

unp_rgs_32327_kensington_047.jpg

unp_rgs_32327_kensington_047.jpg

4649 ms

20170705_rgs_planetearth2_18-06-16_edited.jpg

20170705_rgs_planetearth2_18-06-16_edited.jpg

5071 ms

fbevents.js

fbevents.js

33 ms

d

d

47 ms

d

d

102 ms

d

d

275 ms

otBannerSdk.js

otBannerSdk.js

31 ms

Accessibility Review

rgs.org accessibility score

94

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

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

Best Practices

rgs.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

rgs.org SEO score

85

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

rgs.org

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