3.6 sec in total
295 ms
2.2 sec
1.1 sec
Welcome to story.be homepage info - get ready to check Story best content for Belgium right away, or after learning these important things about story.be
Elke week staat Story boordevol boeiende artikels van bekend Vlaanderen en Hollywood. ✓ 12, 24 of 36 maanden. ✓ Iedere week aan huis geleverd.
Visit story.beWe analyzed Story.be page load time and found that the first response time was 295 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.
story.be performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value5.1 s
25/100
25%
Value7.6 s
26/100
10%
Value20 ms
100/100
30%
Value0.07
96/100
15%
Value4.7 s
80/100
10%
295 ms
43 ms
145 ms
84 ms
39 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Story.be, 16% (22 requests) were made to Static0.hln.be and 12% (17 requests) were made to Static1.hln.be. The less responsive or slowest element that took the longest time to load (477 ms) relates to the external source Analytics.twitter.com.
Page size can be reduced by 1.7 MB (58%)
3.0 MB
1.3 MB
In fact, the total size of Story.be main page is 3.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. 75% 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. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 101.6 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 101.6 kB or 79% of the original size.
Potential reduce by 61.9 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. Story images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 71% of the original size.
Potential reduce by 266.1 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. Story.be needs all CSS files to be minified and compressed as it can save up to 266.1 kB or 82% of the original size.
Number of requests can be reduced by 61 (45%)
136
75
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Story. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
story.be
295 ms
index.dhtml
43 ms
hln-www.head.top.min.js
145 ms
ssoconnect.js
84 ms
site-min.css
39 ms
hln-www.min.css
33 ms
hln-www.head.bottom.min.js
328 ms
widgets.js
95 ms
integration_new.js
327 ms
autodeploy.css
11 ms
numeral.js
33 ms
app.js
62 ms
conversion.js
29 ms
hln-www.body.min.js
22 ms
oct.js
119 ms
gpt.js
7 ms
pubads_impl_82.js
9 ms
container.html
186 ms
gtm.js
164 ms
webfont.js
112 ms
fbds.js
85 ms
Interstitial_SiteBanner_HLN.jpg
46 ms
logo_hetlaatstenieuws.gif
45 ms
hln_logo_story.png
150 ms
terug_naar_hln_story.png
207 ms
logo_performix_50x36.jpg
44 ms
media_l_8487257.jpg
209 ms
media_l_8487153.jpg
208 ms
media_l_8487086.jpg
298 ms
teaser_1_2_8455295.jpg
308 ms
teaser_1_2_8350388.jpg
274 ms
weather_weathertype04.png
140 ms
weather_weathertype02.png
285 ms
media_l_8456054.jpg
404 ms
media_l_8466911.jpg
403 ms
media_l_8456002.jpg
334 ms
media_l_8386077.jpg
414 ms
media_l_8386019.jpg
426 ms
media_l_8378967.jpg
425 ms
media_l_8378663.jpg
461 ms
bt_play.png
412 ms
cim_internet.png
411 ms
media_l_8487217.jpg
311 ms
media_l_8466956.jpg
192 ms
media_l_8386781.jpg
310 ms
media_l_8386154.jpg
140 ms
media_l_8386882.jpg
138 ms
media_l_8386272.jpg
288 ms
media_l_8378834.jpg
280 ms
logo_dpd.jpg
195 ms
teaser_1_2_8426295.png
190 ms
weather_weathertype04.png
30 ms
media_xll_8467014.jpg
137 ms
media_l_8466981.jpg
134 ms
media_l_8453289.jpg
135 ms
media_l_8386106.jpg
189 ms
bt_play.png
62 ms
media_l_8386553.jpg
137 ms
media_l_8386535.jpg
273 ms
media_l_8386002.jpg
272 ms
media_xll_8385983.jpg
274 ms
media_l_8378724.jpg
274 ms
gopress.png
188 ms
license2publish.png
291 ms
media_xll_8487307.jpg
133 ms
media_l_8467048.jpg
183 ms
media_xll_8455978.jpg
184 ms
media_xll_8386517.jpg
183 ms
bt_play.png
56 ms
media_l_8386069.jpg
133 ms
media_l_8385954.jpg
287 ms
media_l_8383281.jpg
271 ms
xgemius.js
317 ms
Interstitial_SiteBanner_HLN.jpg
167 ms
sdk.js
101 ms
font.css
17 ms
font_you.css
18 ms
overlayBg.png
147 ms
ads
183 ms
analytics.js
71 ms
9327.js
71 ms
controltag
144 ms
uts-no-vea.min.js
409 ms
fbevents.js
68 ms
128 ms
collect
155 ms
54 ms
40 ms
BebasNeue-webfont.woff
30 ms
Ubuntu-R-webfont.woff
47 ms
xd_arbiter.php
126 ms
xd_arbiter.php
183 ms
controltag.js.f8e94fa978cc2569e4b4423df4245d7e
45 ms
fpdata.js
104 ms
collect
74 ms
black_40p.png
44 ms
lsget.html
461 ms
interactive_search_open_story.png
335 ms
icon_bn_drop.png
22 ms
BebasNeue-Book.woff
27 ms
agenda-boldcondensed-webfont.woff
44 ms
sprite_header.png
398 ms
sprite_header.png
14 ms
p.js
17 ms
agenda-mediumcondensed-webfont.woff
188 ms
co2stats_badge.png
191 ms
187 ms
index.dhtml
201 ms
outbrain.js
282 ms
adsct
477 ms
adsct
248 ms
esf.js
207 ms
20087
202 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
370 ms
s
163 ms
u
151 ms
authenticated
251 ms
245 ms
hln.be
126 ms
20214
58 ms
;ord=1458497795237
152 ms
xd_arbiter.php
124 ms
like.php
140 ms
ptrack-v0.4.10-engaged-time.js
47 ms
bcn
202 ms
jquery.min.js
79 ms
jquery.cookie.min.js
100 ms
easyXDM.min.js
100 ms
like.php
111 ms
qeKvIRsJabD.js
200 ms
LVx-xkvaJ0b.png
213 ms
rexdot.js
123 ms
58 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.nl.html
58 ms
collect
18 ms
optout_check
54 ms
get
54 ms
chartbeat.js
58 ms
29 ms
jot
93 ms
ping
11 ms
story.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
Image elements do not have [alt] attributes
story.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
story.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
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Story.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Story.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.
story.be
Open Graph description is not detected on the main page of Story. 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: