Tools & Wizards About Us
florugby.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    55% of websites

florugby.com

Rugby News | Games, Videos & Highlights - FloRugby

Page Load Speed

2.4 sec in total

First Response

33 ms

Resources Loaded

921 ms

Page Rendered

1.5 sec

florugby.com screenshot

About Website

Visit florugby.com now to see the best up-to-date Flo Rugby content for United States and also check out these interesting facts you probably never knew about florugby.com

Rugby games, videos, news, & articles. Watch & stream live rugby matches on FloRugby.com. Youth & professional rugby coverage.

Visit florugby.com

Key Findings

We analyzed Florugby.com page load time and found that the first response time was 33 ms and then it took 2.4 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

florugby.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.7 s

0/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value7,570 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value45.4 s

0/100

10%

Network Requests Diagram

www.florugby.com

33 ms

A5399711-5f11-4f2e-be8c-01f2bd8b50fd1.js

66 ms

osano.js

162 ms

osano-flo.js

14 ms

grumi-ip.js

53 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 10% of them (11 requests) were addressed to the original Florugby.com, 71% (75 requests) were made to D2779tscntxxsw.cloudfront.net and 2% (2 requests) were made to Rumcdn.geoedge.be. The less responsive or slowest element that took the longest time to load (554 ms) relates to the external source Siop.flosports.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.8 MB (43%)

Content Size

6.6 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Florugby.com main page is 6.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 441.9 kB

  • Original 494.1 kB
  • After minification 486.1 kB
  • After compression 52.2 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 441.9 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.1 MB
  • After minification 2.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. Flo Rugby images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 2.4 MB

  • Original 3.9 MB
  • After minification 3.9 MB
  • After compression 1.5 MB

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 2.4 MB or 61% of the original size.

CSS Optimization

-0%

Potential reduce by 77 B

  • Original 62.6 kB
  • After minification 62.6 kB
  • After compression 62.5 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. Florugby.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (20%)

Requests Now

103

After Optimization

82

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.florugby.com

www.florugby.com

33 ms

A5399711-5f11-4f2e-be8c-01f2bd8b50fd1.js

A5399711-5f11-4f2e-be8c-01f2bd8b50fd1.js

66 ms

osano.js

osano.js

162 ms

osano-flo.js

osano-flo.js

14 ms

grumi-ip.js

grumi-ip.js

53 ms

client

client

130 ms

apstag.js

apstag.js

56 ms

gpt.js

gpt.js

129 ms

redfast.js

redfast.js

52 ms

styles.0ee9a89dd67408a7.css

styles.0ee9a89dd67408a7.css

40 ms

sdk.js

sdk.js

45 ms

ima3.js

ima3.js

59 ms

runtime.e199708745846d45.js

runtime.e199708745846d45.js

32 ms

polyfills.a6ca7a776e810063.js

polyfills.a6ca7a776e810063.js

43 ms

iframe-resizer.82ab8d56f19dd35e.js

iframe-resizer.82ab8d56f19dd35e.js

43 ms

main.d53d9f8d1edd5e81.js

main.d53d9f8d1edd5e81.js

73 ms

d

d

18 ms

ope-pdmp.js

ope-pdmp.js

231 ms

siop.min.js

siop.min.js

554 ms

mx4e0dl5d9

mx4e0dl5d9

553 ms

icon-sprite-b14660e8.svg

icon-sprite-b14660e8.svg

193 ms

667c895387dde.png

667c895387dde.png

413 ms

logo-sprite-f1c55f45.svg

logo-sprite-f1c55f45.svg

134 ms

663d348e8a8bf.png

663d348e8a8bf.png

429 ms

63864acbd2585.png

63864acbd2585.png

471 ms

64e8fc6816234.png

64e8fc6816234.png

482 ms

63174bc808938.png

63174bc808938.png

482 ms

66d356d4dec80.png

66d356d4dec80.png

487 ms

66d363bad63ae.png

66d363bad63ae.png

484 ms

66d363bad63ae.png

66d363bad63ae.png

482 ms

8271851beda508011263bdd333d905823ed8ef5c117.png

8271851beda508011263bdd333d905823ed8ef5c117.png

490 ms

66d1fa83c266e.png

66d1fa83c266e.png

484 ms

66d2f8f492554.png

66d2f8f492554.png

484 ms

66d2f8f492554.png

66d2f8f492554.png

485 ms

05a0c21c951faa6bffe17ff78268b0d677aa6d39739.png

05a0c21c951faa6bffe17ff78268b0d677aa6d39739.png

488 ms

66d1957c25d2c.png

66d1957c25d2c.png

487 ms

66d1957c25d2c.png

66d1957c25d2c.png

488 ms

66d055281083e.png

66d055281083e.png

489 ms

66d055281083e.png

66d055281083e.png

492 ms

66cf3a183cb70.png

66cf3a183cb70.png

490 ms

66cf3a183cb70.png

66cf3a183cb70.png

492 ms

66cde5a6cca97.png

66cde5a6cca97.png

490 ms

66cde5a6cca97.png

66cde5a6cca97.png

493 ms

66cde37895bd0.png

66cde37895bd0.png

508 ms

66cdc317e558b.png

66cdc317e558b.png

495 ms

66cdc317e558b.png

66cdc317e558b.png

496 ms

66cdb6f9cec7a.png

66cdb6f9cec7a.png

494 ms

66cdb6f9cec7a.png

66cdb6f9cec7a.png

495 ms

66cc9e58a15d9.png

66cc9e58a15d9.png

496 ms

66cc9e58a15d9.png

66cc9e58a15d9.png

508 ms

66cc800b5953d.png

66cc800b5953d.png

509 ms

66cc800b5953d.png

66cc800b5953d.png

508 ms

66cba4d8dc033.png

66cba4d8dc033.png

511 ms

66cba4d8dc033.png

66cba4d8dc033.png

510 ms

66cb6324babc7.png

66cb6324babc7.png

516 ms

66cb6324babc7.png

66cb6324babc7.png

515 ms

66cb625c0a4f3.png

66cb625c0a4f3.png

510 ms

66cb625c0a4f3.png

66cb625c0a4f3.png

515 ms

pubads_impl.js

pubads_impl.js

94 ms

brig.umd.min.App.js

brig.umd.min.App.js

56 ms

sdk.js

sdk.js

54 ms

uni-neue-regular-webfont.woff

uni-neue-regular-webfont.woff

292 ms

uni-neue-heavy-webfont.woff

uni-neue-heavy-webfont.woff

292 ms

grumi.js

grumi.js

339 ms

66c9f78fc50fb.png

66c9f78fc50fb.png

93 ms

66c9f78fc50fb.png

66c9f78fc50fb.png

78 ms

66c72e68c18c6.png

66c72e68c18c6.png

48 ms

settings

settings

35 ms

clarity.js

clarity.js

49 ms

66c72e68c18c6.png

66c72e68c18c6.png

39 ms

66c5ad7ce32cd.png

66c5ad7ce32cd.png

40 ms

66c5ad7ce32cd.png

66c5ad7ce32cd.png

39 ms

66c5a9357eb2a.png

66c5a9357eb2a.png

39 ms

66c5a9357eb2a.png

66c5a9357eb2a.png

39 ms

66c59ece1ca68.png

66c59ece1ca68.png

39 ms

66c59ece1ca68.png

66c59ece1ca68.png

39 ms

66c4c2d01565c.png

66c4c2d01565c.png

39 ms

66c4c2d01565c.png

66c4c2d01565c.png

38 ms

66c4c0131f86a.png

66c4c0131f86a.png

38 ms

66c4c0131f86a.png

66c4c0131f86a.png

37 ms

66c4b4635ba11.png

66c4b4635ba11.png

38 ms

66c4b4635ba11.png

66c4b4635ba11.png

37 ms

42c4aca18b46651522d7c86dbf5d71c4758fd1b2533.png

42c4aca18b46651522d7c86dbf5d71c4758fd1b2533.png

38 ms

66c305e9683c0.png

66c305e9683c0.png

37 ms

66c305e9683c0.png

66c305e9683c0.png

39 ms

0cf50cbd03daddeea93de6119f8e9e0d66f910d5717.png

0cf50cbd03daddeea93de6119f8e9e0d66f910d5717.png

36 ms

66bfb0c330e76.png

66bfb0c330e76.png

36 ms

66bfb0c330e76.png

66bfb0c330e76.png

37 ms

66be081cd85b7.png

66be081cd85b7.png

37 ms

66be081cd85b7.png

66be081cd85b7.png

36 ms

66be44287e497.png

66be44287e497.png

36 ms

66be44287e497.png

66be44287e497.png

33 ms

66bb4bd6b0637.png

66bb4bd6b0637.png

31 ms

66bb4bd6b0637.png

66bb4bd6b0637.png

32 ms

66bb1d7118301.png

66bb1d7118301.png

33 ms

66b790b78550a.png

66b790b78550a.png

31 ms

66b790b78550a.png

66b790b78550a.png

30 ms

02500543ae2743ad9d18eff6037028e343ef20b2115.png

02500543ae2743ad9d18eff6037028e343ef20b2115.png

32 ms

66b717a879a73.png

66b717a879a73.png

30 ms

66b717a879a73.png

66b717a879a73.png

28 ms

800e24fbcd148dbdaa3b7e4186ea9720674199ea865.png

800e24fbcd148dbdaa3b7e4186ea9720674199ea865.png

29 ms

66b6ccb63305f.png

66b6ccb63305f.png

29 ms

66b6ccb63305f.png

66b6ccb63305f.png

26 ms

66b611dfe344f.png

66b611dfe344f.png

29 ms

66b611dfe344f.png

66b611dfe344f.png

28 ms

c.gif

c.gif

7 ms

Accessibility Review

florugby.com accessibility score

66

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-*] attributes do not match their roles

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

High

Links do not have a discernible name

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

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

florugby.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 Florugby.com 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 Florugby.com 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

florugby.com

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