Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

ruum.com

#1 Monthly Clothing Subscription Boxes For Kids | kidpik

Page Load Speed

743 ms in total

First Response

25 ms

Resources Loaded

517 ms

Page Rendered

201 ms

ruum.com screenshot

About Website

Welcome to ruum.com homepage info - get ready to check Ruum best content for United States right away, or after learning these important things about ruum.com

kidpik is a free personal styling service for kids that delivers clothing subscription boxes to your home. Each box includes 3 mix-&-match outfits.

Visit ruum.com

Key Findings

We analyzed Ruum.com page load time and found that the first response time was 25 ms and then it took 718 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

ruum.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value3,530 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

ruum.com

25 ms

www.kidpik.com

95 ms

gtm.js

76 ms

otSDKStub.js

44 ms

jquery-3.6.4.min.js

15 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ruum.com, 56% (29 requests) were made to Kidpik.com and 15% (8 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (197 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 103.6 kB (19%)

Content Size

541.9 kB

After Optimization

438.2 kB

In fact, the total size of Ruum.com main page is 541.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. 70% of websites need less resources to load. Javascripts take 320.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 94.7 kB

  • Original 114.8 kB
  • After minification 114.2 kB
  • After compression 20.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 94.7 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 18 B

  • Original 106.2 kB
  • After minification 106.2 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. Ruum images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 8.9 kB

  • Original 320.9 kB
  • After minification 320.9 kB
  • After compression 312.0 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 24 (49%)

Requests Now

49

After Optimization

25

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ruum. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

ruum.com accessibility score

81

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

High

Image elements do not have [alt] attributes

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

[id] attributes on active, focusable elements are not unique

Best Practices

ruum.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ruum.com SEO score

76

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ruum.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 Ruum.com main page’s claimed encoding is . 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 data is detected on the main page of Ruum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: