Tools & Wizards About Us
tom-tailor.be screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

tom-tailor.be

TOM TAILOR Online Shop - Mode voor dames, heren en kinderen

Page Load Speed

4.1 sec in total

First Response

242 ms

Resources Loaded

2.2 sec

Page Rendered

1.6 sec

tom-tailor.be screenshot

About Website

Click here to check amazing TOM TAILOR content for Switzerland. Otherwise, check out these important facts you probably never knew about tom-tailor.be

De ruimste keus aan dames-, heren- en kinderkleding, schoenen en interieurtextiel van TOM TAILOR vind je in de officiële Online Shop.

Visit tom-tailor.be

Key Findings

We analyzed Tom-tailor.be page load time and found that the first response time was 242 ms and then it took 3.9 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

tom-tailor.be performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value4,110 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.2

62/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

tom-tailor.be

242 ms

tom-tailor.be

105 ms

www.tom-tailor.be

931 ms

kameleoon.js

200 ms

install.js

590 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 48% of them (24 requests) were addressed to the original Tom-tailor.be, 36% (18 requests) were made to Res.cloudinary.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (931 ms) belongs to the original domain Tom-tailor.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 925.2 kB (18%)

Content Size

5.1 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Tom-tailor.be main page is 5.1 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 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 923.1 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 108.8 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 923.1 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 1.8 kB

  • Original 3.8 MB
  • After minification 3.8 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. TOM TAILOR images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 250 B

  • Original 245.8 kB
  • After minification 245.8 kB
  • After compression 245.5 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 23 (50%)

Requests Now

46

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tom-tailor.be

tom-tailor.be

242 ms

tom-tailor.be

tom-tailor.be

105 ms

www.tom-tailor.be

www.tom-tailor.be

931 ms

kameleoon.js

kameleoon.js

200 ms

install.js

install.js

590 ms

gtm.js

gtm.js

235 ms

loader.js

loader.js

168 ms

378cd2843d241fd5.css

378cd2843d241fd5.css

215 ms

7b3da5d2afb388a5.css

7b3da5d2afb388a5.css

142 ms

7c1f13b9acd83b13.css

7c1f13b9acd83b13.css

294 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

175 ms

5848.f1dc328e808ee1fd.js

5848.f1dc328e808ee1fd.js

292 ms

1617.5d5babb40472cd1d.js

1617.5d5babb40472cd1d.js

211 ms

7279.0788627fb19ad767.js

7279.0788627fb19ad767.js

289 ms

3653.1cc7eae2b21f18ee.js

3653.1cc7eae2b21f18ee.js

300 ms

5359.0b69b5d38302d37f.js

5359.0b69b5d38302d37f.js

525 ms

979.6f58ae9733fe6645.js

979.6f58ae9733fe6645.js

526 ms

7823.6f2c9c779e649771.js

7823.6f2c9c779e649771.js

525 ms

9615.fcae9276274209d6.js

9615.fcae9276274209d6.js

291 ms

webpack-98f256610bb55388.js

webpack-98f256610bb55388.js

525 ms

framework-3f6ca6aeff951304.js

framework-3f6ca6aeff951304.js

528 ms

main-d5b902894c7b67a4.js

main-d5b902894c7b67a4.js

524 ms

_app-d33ddb208e1ee9a3.js

_app-d33ddb208e1ee9a3.js

774 ms

%5B%5B...slug%5D%5D-032d2adefe025039.js

%5B%5B...slug%5D%5D-032d2adefe025039.js

607 ms

_buildManifest.js

_buildManifest.js

606 ms

_ssgManifest.js

_ssgManifest.js

574 ms

qt7oycsz7o30rcn9idz5

qt7oycsz7o30rcn9idz5

412 ms

976704076

976704076

515 ms

p4e0iqavcg7n4zqysgfa

p4e0iqavcg7n4zqysgfa

481 ms

lqc44izhmi2gjgkg7r0v

lqc44izhmi2gjgkg7r0v

614 ms

sbibvs4i4k1unfyu0jzr

sbibvs4i4k1unfyu0jzr

602 ms

sl7guxoj6uus9dfdgchu

sl7guxoj6uus9dfdgchu

641 ms

uwyymv39za0cbgzmzmor

uwyymv39za0cbgzmzmor

608 ms

epmf9rikx14emf0s1ebm

epmf9rikx14emf0s1ebm

609 ms

qji2geirey6ueenvoa1n.svg

qji2geirey6ueenvoa1n.svg

527 ms

qesz6ullrutq1rjlbqng.svg

qesz6ullrutq1rjlbqng.svg

598 ms

qcag6jkvdn4eou1rmvf2.svg

qcag6jkvdn4eou1rmvf2.svg

602 ms

joxamcgmhu448xdialmd.svg

joxamcgmhu448xdialmd.svg

601 ms

j1mnj8wbs9n0p2aczv7l.svg

j1mnj8wbs9n0p2aczv7l.svg

604 ms

mwm6jrooqe08snxkwgsv.svg

mwm6jrooqe08snxkwgsv.svg

603 ms

ic9jkywj5piw1v2itcgp.svg

ic9jkywj5piw1v2itcgp.svg

613 ms

n8uvaaxrxorowraw4gwd.svg

n8uvaaxrxorowraw4gwd.svg

607 ms

adr2k6wqcl5fsafvgdbi.svg

adr2k6wqcl5fsafvgdbi.svg

609 ms

i3gwb2dup45u3rkjkidf.svg

i3gwb2dup45u3rkjkidf.svg

611 ms

jaxajbw7n72focf15bzl.svg

jaxajbw7n72focf15bzl.svg

900 ms

sprite.svg

sprite.svg

528 ms

rum

rum

470 ms

bundle.js

bundle.js

23 ms

js

js

195 ms

api.js

api.js

74 ms

Accessibility Review

tom-tailor.be accessibility score

89

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

Links do not have a discernible name

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

tom-tailor.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

Missing source maps for large first-party JavaScript

SEO Factors

tom-tailor.be SEO score

100

Search Engine Optimization Advices

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 Tom-tailor.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 Tom-tailor.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

tom-tailor.be

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