10.5 sec in total
3.6 sec
6.4 sec
484 ms
Visit stichtinghartjesdagen.nl now to see the best up-to-date Stichtinghartjesdagen content and also check out these interesting facts you probably never knew about stichtinghartjesdagen.nl
Bijzonder feest in een bijzondere straat
Visit stichtinghartjesdagen.nlWe analyzed Stichtinghartjesdagen.nl page load time and found that the first response time was 3.6 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
stichtinghartjesdagen.nl performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value4.8 s
31/100
25%
Value5.2 s
59/100
10%
Value470 ms
60/100
30%
Value0.144
77/100
15%
Value4.5 s
82/100
10%
3636 ms
240 ms
24 ms
328 ms
335 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 21% of them (18 requests) were addressed to the original Stichtinghartjesdagen.nl, 27% (23 requests) were made to Pbs.twimg.com and 11% (9 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Stichtinghartjesdagen.nl.
Page size can be reduced by 297.4 kB (14%)
2.1 MB
1.8 MB
In fact, the total size of Stichtinghartjesdagen.nl main page is 2.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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 18.4 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 18.4 kB or 73% of the original size.
Potential reduce by 15.6 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. Stichtinghartjesdagen images are well optimized though.
Potential reduce by 112.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 112.7 kB or 57% of the original size.
Potential reduce by 150.8 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. Stichtinghartjesdagen.nl needs all CSS files to be minified and compressed as it can save up to 150.8 kB or 77% of the original size.
Number of requests can be reduced by 32 (41%)
79
47
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stichtinghartjesdagen. 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 from 11 to 1 for CSS and as a result speed up the page load time.
stichtinghartjesdagen.nl
3636 ms
wp-emoji-release.min.js
240 ms
css
24 ms
style.css
328 ms
genericons.css
335 ms
jetpack.css
434 ms
jquery.js
552 ms
jquery-migrate.min.js
245 ms
scripts.js
324 ms
devicepx-jetpack.js
11 ms
gprofiles.js
66 ms
wpgroho.js
233 ms
sharing.js
270 ms
e-201611.js
9 ms
linoharten.jpg
2316 ms
cropped-linoharten-en-titel.jpg
396 ms
303636_487731754570768_662897072_n-300x200.jpg
204 ms
424665_487732081237402_1214633898_n-300x200.jpg
203 ms
zeedijk-helemaal-met-tafels-Hartjesdagen-blanco-195x300.jpg
202 ms
puntenkaart-IMAG1007-179x300.jpg
202 ms
zeedijk-helemaal-met-tafels-Hartjesdagen-omlooproutes-AANGEPAST-300x271.jpg
322 ms
widgets.js
110 ms
1003 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
22 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
23 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
22 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
22 ms
Genericons.svg
492 ms
8AAnjaY2BgYGQAgjO2i86D6AshzNIwGgBAmQUAAAA=
20 ms
hovercard.css
40 ms
services.css
100 ms
g.gif
16 ms
count.json
86 ms
jetpack-count
183 ms
g.gif
71 ms
g.gif
72 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
130 ms
g.gif
9 ms
syndication
94 ms
621975024904372224
196 ms
proxy.jpg
31 ms
proxy.jpg
36 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
33 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
60 ms
qnEYpP2I_normal.jpg
198 ms
CYkI9BBI_normal.jpg
169 ms
-Sm697ub_normal.jpg
99 ms
Wim-20090906-shootluc3_049rt_ct_DETAIL__ct3_normal.jpg
235 ms
Jlqd74CK_normal.jpg
98 ms
93b14068e91a3d230cd17fc1a1c61e6c_normal.jpeg
193 ms
CY7FgSfWsAAkvKp.jpg:small
237 ms
CO2EbMPWcAAMt27.jpg:small
301 ms
CMznHdjUsAE4KT2.jpg:small
236 ms
CMzjgXGUcAAZKyn.jpg:small
238 ms
CMoRSe_UsAAV5hr.jpg:small
273 ms
CMoRSQcUEAAbGT1.jpg:small
306 ms
CMnaNTGU8AAi7rg.jpg:small
314 ms
CMm-tCkVAAAaFf-.jpg:small
328 ms
CMmw9cWUwAQiq0s.jpg:small
322 ms
CMmjRnFUwAAx-hD.jpg:small
326 ms
CMmVg-NUwAApoc7.jpg:small
346 ms
CMmVg3yVEAAUQGC.jpg:small
390 ms
CMmVg2XUwAIHtuI.jpg:small
424 ms
CMiVPsGWoAA-B1D.jpg:small
421 ms
CQ8_e0QW8AAwOr8.jpg:small
424 ms
CQ8_e0RWIAAQsML.jpg:small
453 ms
CQ8_e0YWwAEC-sq.jpg:small
454 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
154 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
171 ms
proxy.jpg
53 ms
proxy.jpg
39 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
24 ms
bootstrap2.min.css
4 ms
ga.js
12 ms
12748238_1045531108803452_686708008_n.jpg
444 ms
11324907_1485099601806435_1510940044_n.jpg
651 ms
11925759_1016203278430765_195989770_n.jpg
970 ms
11849211_489408801223446_1390628745_n.jpg
821 ms
11820478_1460153017624593_1563225898_n.jpg
812 ms
11850384_507066846127286_1587733395_n.jpg
822 ms
11821335_545499398934370_1402562046_n.jpg
881 ms
11848849_1617966128469821_935635711_n.jpg
844 ms
11925899_424633391067932_2053726959_n.jpg
1165 ms
__utm.gif
12 ms
jot.html
28 ms
stichtinghartjesdagen.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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
stichtinghartjesdagen.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
stichtinghartjesdagen.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stichtinghartjesdagen.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 Stichtinghartjesdagen.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.
stichtinghartjesdagen.nl
Open Graph data is detected on the main page of Stichtinghartjesdagen. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: