5.4 sec in total
435 ms
4.7 sec
288 ms
Click here to check amazing L1 content for Netherlands. Otherwise, check out these important facts you probably never knew about l1.nl
L1 | Regionaal nieuws, sport, weer en verkeer uit Limburg, via radio, tv, website en social media, onder het motto Liefde voor Limburg
Visit l1.nlWe analyzed L1.nl page load time and found that the first response time was 435 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
l1.nl performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value4.4 s
40/100
25%
Value6.5 s
39/100
10%
Value3,200 ms
2/100
30%
Value0
100/100
15%
Value14.7 s
8/100
10%
435 ms
999 ms
228 ms
1570 ms
571 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 54% of them (71 requests) were addressed to the original L1.nl, 8% (11 requests) were made to Pagead2.googlesyndication.com and 8% (10 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Npoplayer.omroep.nl.
Page size can be reduced by 1.3 MB (52%)
2.4 MB
1.1 MB
In fact, the total size of L1.nl main page is 2.4 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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 244.7 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 244.7 kB or 78% of the original size.
Potential reduce by 97.5 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. Obviously, L1 needs image optimization as it can save up to 97.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 724.3 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 724.3 kB or 69% of the original size.
Potential reduce by 185.5 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. L1.nl needs all CSS files to be minified and compressed as it can save up to 185.5 kB or 83% of the original size.
Number of requests can be reduced by 45 (37%)
123
78
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of L1. 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.
l1.nl
435 ms
www.l1.nl
999 ms
mobile_redirect.js
228 ms
npoplayer-min.js
1570 ms
css_285157ea4f4a1467a93c8ec1123d5dac.css
571 ms
js_5442c0c2f9b6268082c151e4a9b6bc70.js
799 ms
js_28d211aa98c867a5b0d06c564b46132c.js
232 ms
logo.png
152 ms
twitter.png
390 ms
facebook.png
441 ms
youtube.png
412 ms
linkedin_icon.png
412 ms
l11alaaf_logo_png.png
860 ms
header_website-einzelgangeroptocht.jpg
508 ms
februari2016.jpg
510 ms
ow160229.jpg
509 ms
_bladmuziek_muzieknoten.png
616 ms
24542184393_32e4d3d2c8_k.jpg
506 ms
dab_radio_bruin.jpg
615 ms
programma_gemist.jpg
618 ms
paul_dolhain_2015.jpg
622 ms
politie-logo-nieuw-uniform.jpg
619 ms
gedrukt-in-maastricht.jpg
734 ms
iris_kroes.jpg
733 ms
rjhp-29feb2016.jpg
750 ms
wendyvluggenphotography_-_138.jpg
751 ms
29-februari-vandaag.jpg
752 ms
kat_in_boodschappentas.jpg
842 ms
25217591712_07f3198391_o.jpg
844 ms
thumbnail_2726.jpg
852 ms
koeriersdienst_te_snel2.jpg
855 ms
brandende-kaarsjes-op-een-verjaardagstaart-hd-verjaardag-achtergrond.jpg
858 ms
stuur-weerfoto-in.jpg
960 ms
img_2752_limburg_van_boven_lkink.jpg
962 ms
karin_van_rens.jpg
964 ms
marieke_cobben_212.jpg
965 ms
nachtegaaltje_breed_logo_0.jpg
966 ms
ongerwaeg_opname_0.jpg
967 ms
avondgasten_team_okt_2014.jpg
1097 ms
60secondenl1nws.jpg
1098 ms
wunderbar_zwartzwart.jpg
1099 ms
hubert_van_hoof_2014.jpg
1100 ms
hubertarnold.jpg
1100 ms
gpt.js
21 ms
rssmikle.js
10 ms
pubads_impl_81.js
15 ms
74 ms
ads
265 ms
ads
297 ms
ads
260 ms
container.html
38 ms
jquery.min.js
265 ms
helvet02-webfont.woff
1061 ms
ads
395 ms
ads
540 ms
ads
525 ms
ga.js
254 ms
gerhouben-bos.jpg
803 ms
6274674778810461234
81 ms
15034868103319746408
108 ms
app_ongerwaeg.jpg
783 ms
analytics.js
50 ms
actueel20160216.jpg
773 ms
17032830215903774097
62 ms
osd.js
35 ms
l11alaaf-gezicht-app-gsm-website.jpg
764 ms
p2
24 ms
__utm.gif
40 ms
collect
25 ms
bijeenkomstnetwerken.jpg
701 ms
foto_l1_business_app.jpg
808 ms
zon_6.png
807 ms
zon-met-wolk-regendruppel-en-sneeuwvlok_0.png
809 ms
expansion_embed.js
15 ms
css
59 ms
m_js_controller.js
5 ms
abg.js
25 ms
googlelogo_color_112x36dp.png
26 ms
nessie_icon_tiamat_white.png
23 ms
button_l1_v04.jpg
706 ms
button_l1tv.jpg
729 ms
button_l1radio.jpg
728 ms
button_plateweg.jpg
812 ms
audio-x-generic--light.png
816 ms
x_button_blue2.png
25 ms
s
53 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
67 ms
ajs.php
279 ms
video-x-generic--light.png
715 ms
hot.png
702 ms
audio-x-generic--dark.png
771 ms
lees_meer.png
771 ms
image-x-generic--dark.png
784 ms
video-x-generic--dark.png
693 ms
lees_meer--white.png
716 ms
bg-weather-frontpage.png
708 ms
bg-traffic-frontpage.png
716 ms
extlink.png
715 ms
go-previous-carousel.png
791 ms
go-next-carousel.png
688 ms
carousel-item-active--blue.png
716 ms
carousel-item-not-active.png
715 ms
ow160229.jpg
721 ms
show_ads.js
3 ms
lg.php
35 ms
ca-pub-6304734341067049.js
31 ms
zrt_lookup.html
20 ms
show_ads_impl.js
58 ms
ads
214 ms
osd.js
6 ms
aclk
85 ms
pixel
33 ms
adj
111 ms
beacon
70 ms
pixel
74 ms
pixel
71 ms
Elephants-Static-160x600.jpg
59 ms
lidar.js
13 ms
sbhK2lTE.js
13 ms
cTrvNaRi.html
32 ms
push
103 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
5 ms
sd
12 ms
20 ms
activeview
19 ms
activeview
26 ms
pixel
26 ms
activeview
14 ms
chartbeat.js
18 ms
ui
55 ms
ping
24 ms
l1.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.
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
Links do not have a discernible name
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.
l1.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
Missing source maps for large first-party JavaScript
l1.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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise L1.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 L1.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.
l1.nl
Open Graph data is detected on the main page of L1. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: