Tools & Wizards About Us
roco.cc screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    60% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

roco.cc

ROCO Modelleisenbahn

Page Load Speed

3.4 sec in total

First Response

404 ms

Resources Loaded

2.8 sec

Page Rendered

152 ms

roco.cc screenshot

About Website

Visit roco.cc now to see the best up-to-date ROCO content for Austria and also check out these interesting facts you probably never knew about roco.cc

ROCO Modellbahnen für Generationen, Innovationsführer im Bereich H0

Visit roco.cc

Key Findings

We analyzed Roco.cc page load time and found that the first response time was 404 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

roco.cc performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.525

14/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

roco.cc

404 ms

index.html

666 ms

stylesheet.css

289 ms

screen.css

430 ms

nn.css

434 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 88% of them (46 requests) were addressed to the original Roco.cc, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Roco.cc.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.0 kB (45%)

Content Size

375.9 kB

After Optimization

207.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Roco.cc main page is 375.9 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 144.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 28.8 kB

  • Original 35.2 kB
  • After minification 34.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 28.8 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 5.6 kB

  • Original 144.0 kB
  • After minification 138.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. ROCO images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 75.5 kB

  • Original 129.2 kB
  • After minification 107.3 kB
  • After compression 53.7 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 75.5 kB or 58% of the original size.

CSS Optimization

-87%

Potential reduce by 59.0 kB

  • Original 67.6 kB
  • After minification 54.2 kB
  • After compression 8.6 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. Roco.cc needs all CSS files to be minified and compressed as it can save up to 59.0 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

44

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

roco.cc

roco.cc

404 ms

index.html

index.html

666 ms

stylesheet.css

stylesheet.css

289 ms

screen.css

screen.css

430 ms

nn.css

nn.css

434 ms

common.js

common.js

578 ms

swfobject.js

swfobject.js

439 ms

ajax.js

ajax.js

570 ms

product_top_navi_en.js

product_top_navi_en.js

567 ms

js-image-slider.css

js-image-slider.css

292 ms

js-image-slider.js

js-image-slider.js

294 ms

conversion.js

conversion.js

17 ms

logo_1.gif

logo_1.gif

159 ms

wk_1.gif

wk_1.gif

158 ms

px.gif

px.gif

159 ms

Roco-Startseite_Teaser_Banner_58660.jpg

Roco-Startseite_Teaser_Banner_58660.jpg

630 ms

235464.jpg

235464.jpg

161 ms

e-shop.jpg

e-shop.jpg

158 ms

beginners.jpg

beginners.jpg

304 ms

basket.jpg

basket.jpg

302 ms

Z21_sond_logo.jpg

Z21_sond_logo.jpg

304 ms

ic_Instagram_Glyph_1.gif

ic_Instagram_Glyph_1.gif

305 ms

youtube_1.gif

youtube_1.gif

311 ms

g_plus_1.gif

g_plus_1.gif

453 ms

facebook_1.gif

facebook_1.gif

454 ms

1_001.gif

1_001.gif

454 ms

1_002.gif

1_002.gif

455 ms

1_003.gif

1_003.gif

462 ms

1_004.gif

1_004.gif

604 ms

1_005.gif

1_005.gif

604 ms

1_006.gif

1_006.gif

605 ms

bg_main_left.gif

bg_main_left.gif

594 ms

top_banner.gif

top_banner.gif

601 ms

ic_profil_1.gif

ic_profil_1.gif

739 ms

dropdown-pfeil_1.png

dropdown-pfeil_1.png

738 ms

luppe.png

luppe.png

739 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

1015 ms

dekar-webfont.woff

dekar-webfont.woff

733 ms

loading.gif

loading.gif

750 ms

bg_main_right.gif

bg_main_right.gif

867 ms

bg_main_bottom_l.gif

bg_main_bottom_l.gif

866 ms

bg_main_bottom.gif

bg_main_bottom.gif

867 ms

bg_main_bottom_r.gif

bg_main_bottom_r.gif

883 ms

bg_footer.gif

bg_footer.gif

894 ms

dot_list.gif

dot_list.gif

994 ms

ga.js

ga.js

51 ms

71 ms

__utm.gif

__utm.gif

18 ms

40 ms

collect

collect

54 ms

ajax_basket_req.asp

ajax_basket_req.asp

155 ms

bullet.png

bullet.png

149 ms

Accessibility Review

roco.cc accessibility score

68

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

Image elements do not have [alt] attributes

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

roco.cc best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

roco.cc SEO score

83

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roco.cc can be misinterpreted by Google and other search engines. Our service has detected that German 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 Roco.cc 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

roco.cc

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