Tools & Wizards About Us
worum.org screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

worum.org

Worum

Page Load Speed

1.8 sec in total

First Response

220 ms

Resources Loaded

1.5 sec

Page Rendered

100 ms

worum.org screenshot

About Website

Visit worum.org now to see the best up-to-date Worum content for Germany and also check out these interesting facts you probably never knew about worum.org

worum.org - Das größte unabhängige Fanforum von Werder Bremen. Inklusive Blog, Podcast, Twitter, Shop und Verein.

Visit worum.org

Key Findings

We analyzed Worum.org page load time and found that the first response time was 220 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

worum.org performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value1.9 s

100/100

10%

Network Requests Diagram

worum.org

220 ms

worum.org

459 ms

yuiloader-dom-event.js

192 ms

connection-min.js

286 ms

vbulletin-core.js

381 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 70% of them (16 requests) were addressed to the original Worum.org, 13% (3 requests) were made to Platform.twitter.com and 9% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (497 ms) belongs to the original domain Worum.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.3 kB (11%)

Content Size

144.5 kB

After Optimization

128.2 kB

  • HTML
  • Images

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

HTML Optimization

-72%

Potential reduce by 15.8 kB

  • Original 22.1 kB
  • After minification 19.9 kB
  • After compression 6.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 15.8 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 518 B

  • Original 122.5 kB
  • After minification 122.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. Worum images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 12 (57%)

Requests Now

21

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Worum. 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

worum.org

worum.org

220 ms

worum.org

worum.org

459 ms

yuiloader-dom-event.js

yuiloader-dom-event.js

192 ms

connection-min.js

connection-min.js

286 ms

vbulletin-core.js

vbulletin-core.js

381 ms

css.php

css.php

497 ms

vbulletin_md5.js

vbulletin_md5.js

288 ms

css.php

css.php

384 ms

testheader12.jpg

testheader12.jpg

190 ms

headerraute_bg.png

headerraute_bg.png

285 ms

search.png

search.png

111 ms

navbit-home.png

navbit-home.png

111 ms

widgets.js

widgets.js

83 ms

like.php

like.php

74 ms

newbtn_middle.png

newbtn_middle.png

97 ms

selected-tab-gradient-with-top-alpha.png

selected-tab-gradient-with-top-alpha.png

98 ms

arrow.png

arrow.png

166 ms

generic_button.png

generic_button.png

167 ms

w9py8-RGams.js

w9py8-RGams.js

35 ms

FEppCFCt76d.png

FEppCFCt76d.png

37 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

53 ms

settings

settings

93 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

22 ms

Accessibility Review

worum.org accessibility score

74

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

High

Some elements have a [tabindex] value greater than 0

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

worum.org best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

worum.org SEO score

90

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

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Worum.org can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Worum.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

worum.org

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