3.6 sec in total
254 ms
1.7 sec
1.7 sec
Visit brandos.be now to see the best up-to-date Brandos content and also check out these interesting facts you probably never knew about brandos.be
Your brand outlet. ✔️ fast delivery.
Visit brandos.beWe analyzed Brandos.be page load time and found that the first response time was 254 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
brandos.be performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value7.9 s
3/100
25%
Value8.9 s
15/100
10%
Value5,600 ms
0/100
30%
Value0.012
100/100
15%
Value18.5 s
3/100
10%
254 ms
678 ms
182 ms
291 ms
244 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Brandos.be, 80% (35 requests) were made to Web-assets.footway.com and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (740 ms) relates to the external source Web-assets.footway.com.
Page size can be reduced by 230.1 kB (50%)
458.3 kB
228.2 kB
In fact, the total size of Brandos.be main page is 458.3 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. 60% of websites need less resources to load. HTML takes 291.4 kB which makes up the majority of the site volume.
Potential reduce by 230.1 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 230.1 kB or 79% of the original size.
Potential reduce by 0 B
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. Brandos images are well optimized though.
Number of requests can be reduced by 35 (95%)
37
2
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brandos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and as a result speed up the page load time.
brandos.be
254 ms
be
678 ms
polyfills-5cd94c89d3acac5f.js
182 ms
optimize.js
291 ms
8040.c154d3d9849ec3b2.js
244 ms
985.39c60299c8076d2c.js
154 ms
7902.8c4f0e4126204574.js
245 ms
1148.2a61af80f3a90f89.js
245 ms
273-e81b5c25bc02d20c.js
242 ms
2464-04bfda4d3fb3dc80.js
165 ms
5696-4b5c6ff8f833a1e0.js
285 ms
8333.8f56423627d97056.js
283 ms
2922-9b183dee904e6d36.js
280 ms
8566-3be39cf9e1dd8a83.js
280 ms
1880.d85def109087022f.js
386 ms
9675-5278f90a10fc85ae.js
401 ms
2430.5559050b58c3ce75.js
405 ms
3784.28d334a208a9a86f.js
405 ms
7676.1238ed8f7d4c364f.js
404 ms
3153-1849a31663e7d36b.js
407 ms
4803.a966157a9e8d60f4.js
407 ms
webpack-7dc8e06808ffaa9f.js
395 ms
framework-568b840ecff66744.js
492 ms
main-5d0af15a48abbd86.js
488 ms
_app-81916b138c82b994.js
632 ms
6659-21ea79fba50dbc9a.js
487 ms
5331-dd4296780c6e3d44.js
486 ms
4637-580d0032360b7bd6.js
623 ms
8584-01b719d30d459d1b.js
629 ms
5426-61a22892294aeae8.js
627 ms
5337-8a07e40f4f629f56.js
674 ms
2450-7fc6bf0c2d3ee81d.js
691 ms
2943-3c8a9ba9786b0732.js
671 ms
3272-657e9b9239c10665.js
734 ms
index-c084668850f7e77d.js
732 ms
_buildManifest.js
733 ms
_ssgManifest.js
730 ms
_middlewareManifest.js
740 ms
css
336 ms
default_brandos_br_16_9
674 ms
KFOmCnqEu92Fr1Mu4mxM.woff
545 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
615 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
670 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
670 ms
brandos.be accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
brandos.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
brandos.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brandos.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 Brandos.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.
brandos.be
Open Graph description is not detected on the main page of Brandos. 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: