Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

orzly.com

ORZLY | Pro Gaming Accessories | Switch, PC, Xbox, PlayStation, Stadia– Orzly

Page Load Speed

10 sec in total

First Response

2.5 sec

Resources Loaded

6.6 sec

Page Rendered

799 ms

orzly.com screenshot

About Website

Visit orzly.com now to see the best up-to-date ORZLY content for Canada and also check out these interesting facts you probably never knew about orzly.com

Orzly Official eShop. Innovative high-performance gaming accessories for Nintendo Switch, Switch Lite, Stadia, PC, Xbox & PS4 consoles. Shop cases, chargers, & creative protection solutions with 2-Yea...

Visit orzly.com

Key Findings

We analyzed Orzly.com page load time and found that the first response time was 2.5 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

orzly.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value4,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.721

6/100

15%

TTI (Time to Interactive)

Value25.8 s

0/100

10%

Network Requests Diagram

orzly.com

2535 ms

calendar-win2k-1.css

150 ms

styles.css

234 ms

widgets.css

154 ms

em_cloudzoom.css

151 ms

Our browser made a total of 208 requests to load all elements on the main page. We found that 97% of them (201 requests) were addressed to the original Orzly.com, 2% (5 requests) were made to Google-analytics.com and 1% (2 requests) were made to Static.lipscore.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Orzly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.5 MB (69%)

Content Size

10.9 MB

After Optimization

3.3 MB

In fact, the total size of Orzly.com main page is 10.9 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. 65% of websites need less resources to load. Images take 9.0 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 228.1 kB

  • Original 249.8 kB
  • After minification 185.3 kB
  • After compression 21.7 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. This page needs HTML code to be minified as it can gain 64.5 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 228.1 kB or 91% of the original size.

Image Optimization

-67%

Potential reduce by 6.1 MB

  • Original 9.0 MB
  • After minification 3.0 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. Obviously, ORZLY needs image optimization as it can save up to 6.1 MB or 67% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 932.2 kB

  • Original 1.2 MB
  • After minification 927.3 kB
  • After compression 271.8 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 932.2 kB or 77% of the original size.

CSS Optimization

-82%

Potential reduce by 333.1 kB

  • Original 405.4 kB
  • After minification 328.7 kB
  • After compression 72.3 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. Orzly.com needs all CSS files to be minified and compressed as it can save up to 333.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (39%)

Requests Now

207

After Optimization

126

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

Accessibility Review

orzly.com accessibility score

56

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

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

High

Heading elements are not in a sequentially-descending order

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

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

orzly.com SEO score

82

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orzly.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 Orzly.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

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