4 sec in total
308 ms
3.3 sec
434 ms
Click here to check amazing 4 Cards content. Otherwise, check out these important facts you probably never knew about 4cards.nl
Geboortekaartjes en trouwkaarten in diverse stijlen, altijd bijzonder, uniek en origineel. Hippe of kunstige kaartjes of juist basic en puur.
Visit 4cards.nlWe analyzed 4cards.nl page load time and found that the first response time was 308 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
4cards.nl performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value6.6 s
8/100
25%
Value5.5 s
54/100
10%
Value810 ms
36/100
30%
Value0.004
100/100
15%
Value10.0 s
26/100
10%
308 ms
595 ms
97 ms
192 ms
201 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 85% of them (53 requests) were addressed to the original 4cards.nl, 5% (3 requests) were made to Ajax.googleapis.com and 5% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain 4cards.nl.
Page size can be reduced by 210.3 kB (8%)
2.8 MB
2.6 MB
In fact, the total size of 4cards.nl main page is 2.8 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. 45% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 15.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. This page needs HTML code to be minified as it can gain 2.4 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 15.1 kB or 74% of the original size.
Potential reduce by 62.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. 4 Cards images are well optimized though.
Potential reduce by 98.8 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 98.8 kB or 67% of the original size.
Potential reduce by 34.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. 4cards.nl needs all CSS files to be minified and compressed as it can save up to 34.0 kB or 79% of the original size.
Number of requests can be reduced by 15 (26%)
58
43
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4 Cards. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
4cards.nl
308 ms
www.4cards.nl
595 ms
master.css
97 ms
jquery-ui-1.8.11.custom.css
192 ms
master.css
201 ms
main.css
188 ms
jquery.min.js
27 ms
jquery-ui.min.js
29 ms
sticky.css
188 ms
jquery-ui.css
37 ms
jquery.easing.1.3.js
193 ms
jquery.vticker.js
193 ms
superfish.js
295 ms
main.js
295 ms
jquery.bxslider.js
313 ms
prijs_calculator.js
294 ms
dc.js
30 ms
gtm.js
58 ms
background.jpg
2143 ms
bg-wrapper.gif
845 ms
ico-basket.png
149 ms
bullet_big.png
152 ms
h-heart.png
153 ms
logo.png
162 ms
img-geam.png
246 ms
enveloppen-1.png
244 ms
bg-slider-top.png
338 ms
bg-slider-left.png
266 ms
bg-slider-right.png
431 ms
bg-slider-bottom.png
433 ms
slide-label01.png
364 ms
slide-label02.png
443 ms
banner-revista.png
779 ms
bannerankekleurensite.png
554 ms
banner-jola2.png
638 ms
geam.png
546 ms
img-thumb.png
836 ms
heart.png
652 ms
f-heart.png
756 ms
tape.png
764 ms
__utm.gif
22 ms
social.png
802 ms
btn-search.png
810 ms
bg-menu.png
832 ms
bg-submenu.png
898 ms
bg-left-menu.png
887 ms
center-content.png
994 ms
btn-geboortekaartjes.png
1440 ms
btn-trouwkaarten.png
923 ms
btn-top10.png
977 ms
btn-reacties.png
1163 ms
bg-title-end.png
1031 ms
bg-fnav-bottom.png
1078 ms
bg-fnav-top.png
1199 ms
rough_typewriter.woff
1333 ms
analytics.js
29 ms
collect
41 ms
collect
61 ms
brain_flower_euro.woff
1108 ms
get_all_cat_prices
1319 ms
bg-top-head.gif
1205 ms
bg-pager.png
1209 ms
4cards.nl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
4cards.nl 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
Page has valid source maps
4cards.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4cards.nl 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 4cards.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.
4cards.nl
Open Graph description is not detected on the main page of 4 Cards. 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: