3.6 sec in total
411 ms
2.8 sec
322 ms
Welcome to fab.nl homepage info - get ready to check Fab best content for Netherlands right away, or after learning these important things about fab.nl
¡Únete a nosotras en octubre de 2022 para tres días y tres noches de fiesta loca! Rockin' bands, wild DJs and bizarre sideshow attractions!
Visit fab.nlWe analyzed Fab.nl page load time and found that the first response time was 411 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
fab.nl performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value5.4 s
20/100
25%
Value11.1 s
5/100
10%
Value5,460 ms
0/100
30%
Value0.113
86/100
15%
Value22.1 s
1/100
10%
411 ms
19 ms
444 ms
356 ms
181 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 77% of them (59 requests) were addressed to the original Fab.nl, 5% (4 requests) were made to Config1.veinteractive.com and 4% (3 requests) were made to V2.zopim.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Fab.nl.
Page size can be reduced by 1.4 MB (24%)
6.0 MB
4.6 MB
In fact, the total size of Fab.nl main page is 6.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 33.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 33.0 kB or 75% of the original size.
Potential reduce by 396.4 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. Fab images are well optimized though.
Potential reduce by 829.1 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 829.1 kB or 79% of the original size.
Potential reduce by 163.0 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. Fab.nl needs all CSS files to be minified and compressed as it can save up to 163.0 kB or 84% of the original size.
Number of requests can be reduced by 29 (41%)
70
41
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fab. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
fab.nl
411 ms
jquery-latest.js
19 ms
f4ff43b07d5bff6cb37fcb20163b8b07.css
444 ms
prototype.js
356 ms
ccard.js
181 ms
validation.js
181 ms
builder.js
182 ms
effects.js
182 ms
dragdrop.js
268 ms
controls.js
269 ms
slider.js
270 ms
js.js
270 ms
form.js
356 ms
menu.js
357 ms
translate.js
357 ms
cookies.js
353 ms
script.js
480 ms
instafeed.min.js
480 ms
campaignCatcher.js
480 ms
distilled.FirstTouch.js
481 ms
slider.js
482 ms
minicart.js
522 ms
carousel.js
523 ms
custom.js
548 ms
ajaxtabs.js
548 ms
custom.css
548 ms
tag.js
119 ms
conversion.js
36 ms
ga.js
26 ms
fab-logo.jpg
283 ms
search.png
129 ms
shopbag.png
129 ms
NEW.jpg
276 ms
shop_tassen_1.jpg
444 ms
PURSES_1.jpg
276 ms
shop_schoenen_2.jpg
458 ms
shop_accessoires.jpg
449 ms
FABIENNECHAPOT_4.jpg
532 ms
File-1455283531.jpg
1334 ms
File-1455283569.jpg
1610 ms
File-1455283602.jpg
1418 ms
BANNER_BIG_RIGHT_SS16_new.jpg
979 ms
BANNER-LEFT-SS16.jpg
898 ms
BANNER-MIDDLE_SS16.jpg
972 ms
BANNER-RIGHT-SS16.jpg
1341 ms
BANNER-LOW_SS16-1.jpg
1327 ms
BANNER-LOW-SS16-2.jpg
1598 ms
BANNER-LOW-SS16-3.jpg
1414 ms
BANNER-LOW-SS16-4.jpg
1418 ms
NIEUWSBRIEF-INSPIRATION.jpg
1430 ms
NIEUWSBRIEF-BANNER-NEW.png
1592 ms
NIEUWSLETTER-INSPIRATION_1.jpg
1594 ms
STORELOCATOR-BANNER-NL_new.jpg
1507 ms
Popup_Voucher_NL_ss16.jpg
1606 ms
volg-facebook.png
1595 ms
volg-twitter.png
1681 ms
volg-pinterest.png
1681 ms
volg-instagram.png
1682 ms
widget_v2.135.js
24 ms
times-italic-webfont.woff
1760 ms
times-roman-webfont.woff
1682 ms
__utm.gif
88 ms
play-pause.png
1664 ms
__$$__stringtable_lang_nl.js
9 ms
collect
71 ms
98 ms
recent
167 ms
PetitaMedium.ttf
1589 ms
capture-apps-4.8.0.js
12 ms
iframeStorage.html
139 ms
35 ms
12797599_1711170562458878_1750228457_n.jpg
239 ms
iframeStorage.js
5 ms
appsmanagerinit
214 ms
avatar_simple_visitor.png
85 ms
aL63HcygAAVYuCCsAAA==
3 ms
f591728d2ed7c881d985248a0b43e85b.css
90 ms
fab.nl 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
fab.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fab.nl SEO score
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
EN
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fab.nl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Dutch language. Our system also found out that Fab.nl 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.
fab.nl
Open Graph description is not detected on the main page of Fab. 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: