Tools & Wizards About Us
rhysy.net screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

rhysy.net

rhysy.net - Home page

Page Load Speed

3.9 sec in total

First Response

616 ms

Resources Loaded

3 sec

Page Rendered

218 ms

rhysy.net screenshot

About Website

Visit rhysy.net now to see the best up-to-date Rhysy content and also check out these interesting facts you probably never knew about rhysy.net

Radio astronomy, galaxy evolution, and data visualisation

Visit rhysy.net

Key Findings

We analyzed Rhysy.net page load time and found that the first response time was 616 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

rhysy.net performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

rhysy.net

616 ms

beng-proxy.js

552 ms

font-awesome.min.css

739 ms

widget-runtime.css

638 ms

deploy.css

642 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 18% of them (6 requests) were addressed to the original Rhysy.net, 53% (18 requests) were made to Strato-editor.com and 29% (10 requests) were made to Fonts.cm4all.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Rhysy.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 388.7 kB (24%)

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rhysy.net main page is 1.6 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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 37.7 kB

  • Original 45.7 kB
  • After minification 45.5 kB
  • After compression 8.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 37.7 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 63.2 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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. Rhysy images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 179.7 kB

  • Original 314.8 kB
  • After minification 314.0 kB
  • After compression 135.1 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 179.7 kB or 57% of the original size.

CSS Optimization

-86%

Potential reduce by 108.1 kB

  • Original 126.1 kB
  • After minification 125.0 kB
  • After compression 18.1 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. Rhysy.net needs all CSS files to be minified and compressed as it can save up to 108.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (77%)

Requests Now

22

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rhysy.net

rhysy.net

616 ms

beng-proxy.js

beng-proxy.js

552 ms

font-awesome.min.css

font-awesome.min.css

739 ms

widget-runtime.css

widget-runtime.css

638 ms

deploy.css

deploy.css

642 ms

slideshow-common.css

slideshow-common.css

645 ms

jquery.js

jquery.js

794 ms

prototype.js

prototype.js

753 ms

legacy.js

legacy.js

742 ms

widget-runtime.js

widget-runtime.js

849 ms

slideshow-common.js

slideshow-common.js

749 ms

deploy.js

deploy.js

846 ms

uro-min.js

uro-min.js

846 ms

main.css

main.css

855 ms

vars.css

vars.css

856 ms

vars.css

vars.css

534 ms

effects.js

effects.js

756 ms

cm-templates-global-script.js

cm-templates-global-script.js

756 ms

show.js

show.js

149 ms

css

css

303 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9gTuoxDkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9gTuoxDkj.ttf

727 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9szuoxDkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9szuoxDkj.ttf

771 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r93zuoxDkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r93zuoxDkj.ttf

739 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9XzyoxDkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9XzyoxDkj.ttf

708 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9ZjyoxDkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9ZjyoxDkj.ttf

743 ms

goksH6L7AUFrRvV44HVjQkqn.ttf

goksH6L7AUFrRvV44HVjQkqn.ttf

604 ms

gokpH6L7AUFrRvV44HVrv2m3kdxA.ttf

gokpH6L7AUFrRvV44HVrv2m3kdxA.ttf

830 ms

gokpH6L7AUFrRvV44HVrk263kdxA.ttf

gokpH6L7AUFrRvV44HVrk263kdxA.ttf

844 ms

gokpH6L7AUFrRvV44HVr92-3kdxA.ttf

gokpH6L7AUFrRvV44HVr92-3kdxA.ttf

858 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

311 ms

_pixel.img

_pixel.img

133 ms

LAB%20volumetric%204.png

LAB%20volumetric%204.png

1298 ms

websitelogo.png

websitelogo.png

201 ms

picture-200

picture-200

213 ms

Accessibility Review

rhysy.net accessibility score

60

Accessibility Issues

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

Buttons do not have an accessible name

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

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

rhysy.net 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

rhysy.net SEO score

92

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rhysy.net 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 Rhysy.net 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

rhysy.net

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