Tools & Wizards About Us
inno.be screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

inno.be

INNO | Mode, Wonen & Meer | Shoppen Online

Page Load Speed

11.4 sec in total

First Response

656 ms

Resources Loaded

2.7 sec

Page Rendered

8 sec

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 bij INNO online of in één van de 16 winkels. 1600+ 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 656 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

inno.be performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,290 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.223

56/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

home

656 ms

main.js

77 ms

campaignBannerIS.js

40 ms

productTile.js

48 ms

gtm.js

82 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 86% of them (51 requests) were addressed to the original Inno.be, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Js.stripe.com. The less responsive or slowest element that took the longest time to load (656 ms) belongs to the original domain Inno.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 396.2 kB (2%)

Content Size

19.9 MB

After Optimization

19.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inno.be main page is 19.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. Only a small number of websites need less resources to load. Images take 19.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 389.6 kB

  • Original 433.6 kB
  • After minification 433.0 kB
  • After compression 44.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 389.6 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 19.1 MB
  • After minification 19.1 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. INNO images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 6.5 kB

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

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 57.3 kB
  • After minification 57.3 kB
  • After compression 57.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. Inno.be has all CSS files already compressed.

Requests Breakdown

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

Requests Now

53

After Optimization

40

  • Images
  • JavaScript
  • CSS

The browser has sent 53 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 14 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

home

home

656 ms

main.js

main.js

77 ms

campaignBannerIS.js

campaignBannerIS.js

40 ms

productTile.js

productTile.js

48 ms

gtm.js

gtm.js

82 ms

gtm.js

gtm.js

73 ms

47 ms

api.js

api.js

36 ms

global.css

global.css

171 ms

klarna.js

klarna.js

32 ms

easysize.js

easysize.js

464 ms

collect.js

collect.js

288 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

32 ms

dwac-21.7.js

dwac-21.7.js

32 ms

gretel.min.js

gretel.min.js

33 ms

NL-Discount_banner-mobilev85.png

NL-Discount_banner-mobilev85.png

145 ms

NL-Discount_banner-tabletv85.png

NL-Discount_banner-tabletv85.png

145 ms

NL-Discount_banner-desktopv85.png

NL-Discount_banner-desktopv85.png

144 ms

3yearsinnobebanner.png

3yearsinnobebanner.png

153 ms

NL-Discount_banner-mobilev86.png

NL-Discount_banner-mobilev86.png

146 ms

NL-Discount_banner-tabletv86.png

NL-Discount_banner-tabletv86.png

146 ms

NL-Discount_banner-desktopv86.png

NL-Discount_banner-desktopv86.png

154 ms

More&More.png

More&More.png

147 ms

RioDelSol.png

RioDelSol.png

149 ms

VilleroyBoch.png

VilleroyBoch.png

148 ms

Garcia.png

Garcia.png

154 ms

MyJewellery.png

MyJewellery.png

155 ms

Robeez.png

Robeez.png

159 ms

LeTempsDesCerises.png

LeTempsDesCerises.png

156 ms

Megami.png

Megami.png

161 ms

Iitala.png

Iitala.png

157 ms

MaisonToufet.png

MaisonToufet.png

159 ms

Mr%20C%C3%A9lestin.png

Mr%20C%C3%A9lestin.png

160 ms

Knuffle.png

Knuffle.png

162 ms

LaurentDavid.png

LaurentDavid.png

163 ms

PSPoelman.png

PSPoelman.png

163 ms

ByNouk.png

ByNouk.png

166 ms

Zero2.png

Zero2.png

164 ms

Toms.png

Toms.png

165 ms

HappyGarden.png

HappyGarden.png

226 ms

Dutch%20D2.png

Dutch%20D2.png

167 ms

9.jpg

9.jpg

230 ms

Vertica_5.jpg

Vertica_5.jpg

224 ms

MORELLATO_SECTOR_2_0025.jpg

MORELLATO_SECTOR_2_0025.jpg

234 ms

e123b21712784243a484635a36736024.jpg

e123b21712784243a484635a36736024.jpg

228 ms

Lisca%20Selection%20Grace%2010329_12327_11053_28.jpg

Lisca%20Selection%20Grace%2010329_12327_11053_28.jpg

227 ms

Polo.png

Polo.png

232 ms

GiftCard2.png

GiftCard2.png

236 ms

LoyaltyCard2.png

LoyaltyCard2.png

237 ms

BrandsNL2.png

BrandsNL2.png

248 ms

usp.svg

usp.svg

235 ms

icons.svg

icons.svg

102 ms

icons.svg

icons.svg

104 ms

font.woff

font.woff

83 ms

font.woff

font.woff

568 ms

font.woff

font.woff

143 ms

font.woff

font.woff

61 ms

font.woff

font.woff

558 ms

t2s.min.js

t2s.min.js

100 ms

Accessibility Review

inno.be accessibility score

80

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.

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

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>).

Best Practices

inno.be best practices score

83

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

High

Page has valid source maps

SEO Factors

inno.be SEO score

85

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • 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 it matches the claimed language. 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

inno.be

Open Graph data is detected on the main page of INNO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: