Report Summary

  • 19

    Performance

    Renders faster than
    37% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

inno.be

INNO | Mode, Wonen & Meer | Shoppen Online

Page Load Speed

4.6 sec in total

First Response

95 ms

Resources Loaded

4.4 sec

Page Rendered

113 ms

inno.be screenshot

About Website

Welcome to inno.be homepage info - get ready to check INNO best content for Belgium right away, or after learning these important things about inno.be

Ervaar de ultieme shoppingervaring van INNO online of in één van de 16 winkels. 800+ topmerken in Fashion & More. Shop altijd de nieuwste collecties.

Visit inno.be

Key Findings

We analyzed Inno.be page load time and found that the first response time was 95 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

inno.be performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

1/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value2,940 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value18.3 s

4/100

10%

Network Requests Diagram

select-language

95 ms

css.css

258 ms

css2.css

523 ms

html5shiv.js

277 ms

respond.min.js

343 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 47% of them (8 requests) were addressed to the original Inno.be, 24% (4 requests) were made to Google-analytics.com and 12% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (959 ms) belongs to the original domain Inno.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.5 kB (7%)

Content Size

123.4 kB

After Optimization

114.9 kB

In fact, the total size of Inno.be main page is 123.4 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. Only 10% of websites need less resources to load. Images take 92.8 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 5.7 kB

  • Original 9.2 kB
  • After minification 9.2 kB
  • After compression 3.6 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 5.7 kB or 61% of the original size.

Image Optimization

-3%

Potential reduce by 2.8 kB

  • Original 92.8 kB
  • After minification 90.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. INNO images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 88 B

  • Original 21.3 kB
  • After minification 21.3 kB
  • After compression 21.3 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 5 (45%)

Requests Now

11

After Optimization

6

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

Accessibility Review

inno.be accessibility score

70

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

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

High

ARIA IDs are not unique

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

inno.be best practices score

85

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

Browser errors were logged to the console

SEO Factors

inno.be SEO score

83

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

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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