Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

georss.org

The principles, origins, underlying models and GeoRSS feeds use

Page Load Speed

472 ms in total

First Response

103 ms

Resources Loaded

272 ms

Page Rendered

97 ms

georss.org screenshot

About Website

Click here to check amazing GeoRSS content. Otherwise, check out these important facts you probably never knew about georss.org

Learn about some of the underlying models and applications of GeoRSS. Get tips on how to implement all of them on a personal website with special skills.

Visit georss.org

Key Findings

We analyzed Georss.org page load time and found that the first response time was 103 ms and then it took 369 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

georss.org performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

georss.org

103 ms

www.georss.org

102 ms

css

23 ms

global.css

4 ms

somerights20.gif

9 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 70% of them (7 requests) were addressed to the original Georss.org, 10% (1 request) were made to Fonts.googleapis.com and 10% (1 request) were made to Creativecommons.org. The less responsive or slowest element that took the longest time to load (103 ms) belongs to the original domain Georss.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.1 kB (40%)

Content Size

17.7 kB

After Optimization

10.6 kB

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

HTML Optimization

-69%

Potential reduce by 4.5 kB

  • Original 6.5 kB
  • After minification 5.8 kB
  • After compression 2.1 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 744 B, which is 11% 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 4.5 kB or 69% of the original size.

Image Optimization

-9%

Potential reduce by 783 B

  • Original 8.8 kB
  • After minification 8.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. GeoRSS images are well optimized though.

CSS Optimization

-76%

Potential reduce by 1.8 kB

  • Original 2.3 kB
  • After minification 1.5 kB
  • After compression 558 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. Georss.org needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 76% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GeoRSS. According to our analytics all requests are already optimized.

Accessibility Review

georss.org accessibility score

88

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

georss.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

georss.org SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Georss.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Georss.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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