Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

rizzo.se

Rizzo.se | Väskor, resväskor & accessoarer online - Shoppa nu

Page Load Speed

5 sec in total

First Response

399 ms

Resources Loaded

4.4 sec

Page Rendered

157 ms

rizzo.se screenshot

About Website

Welcome to rizzo.se homepage info - get ready to check Rizzo best content for Sweden right away, or after learning these important things about rizzo.se

Shoppa väskor, resväskor och handskar på Rizzo.se. När du shoppar på Rizzo.se får du fri frakt på beställningar över 599 kr och fri retur till butik!

Visit rizzo.se

Key Findings

We analyzed Rizzo.se page load time and found that the first response time was 399 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

rizzo.se performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value19.3 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,930 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.498

16/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

rizzo.se

399 ms

www.neye.se

1088 ms

uc.js

138 ms

znpscaru.js

923 ms

bundle.css

971 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Rizzo.se, 35% (19 requests) were made to Neye.se and 31% (17 requests) were made to Neye-image-cdn.azureedge.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Neye.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 837.4 kB (42%)

Content Size

2.0 MB

After Optimization

1.2 MB

In fact, the total size of Rizzo.se main page is 2.0 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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 135.5 kB

  • Original 153.7 kB
  • After minification 142.7 kB
  • After compression 18.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 135.5 kB or 88% of the original size.

Image Optimization

-6%

Potential reduce by 44.9 kB

  • Original 777.5 kB
  • After minification 732.6 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. Rizzo images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 657.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 413.9 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 657.0 kB or 61% of the original size.

CSS Optimization

-1%

Potential reduce by 13 B

  • Original 929 B
  • After minification 929 B
  • After compression 916 B

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. Rizzo.se has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (51%)

Requests Now

49

After Optimization

24

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

Accessibility Review

rizzo.se accessibility score

77

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

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.

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

rizzo.se best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

rizzo.se SEO score

84

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

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

    SV

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rizzo.se can be misinterpreted by Google and other search engines. Our service has detected that Swedish 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 Rizzo.se 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 description is not detected on the main page of Rizzo. 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: