5.7 sec in total
1.1 sec
4.2 sec
463 ms
Welcome to tolocal.nl homepage info - get ready to check To Local best content right away, or after learning these important things about tolocal.nl
Visit tolocal.nlWe analyzed Tolocal.nl page load time and found that the first response time was 1.1 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tolocal.nl performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value10.0 s
0/100
25%
Value7.2 s
30/100
10%
Value1,020 ms
26/100
30%
Value0.023
100/100
15%
Value10.3 s
24/100
10%
1082 ms
41 ms
81 ms
94 ms
172 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 85% of them (50 requests) were addressed to the original Tolocal.nl, 8% (5 requests) were made to Vjs.zencdn.net and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Tolocal.nl.
Page size can be reduced by 421.7 kB (29%)
1.4 MB
1.0 MB
In fact, the total size of Tolocal.nl main page is 1.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. 35% of websites need less resources to load. Images take 844.9 kB which makes up the majority of the site volume.
Potential reduce by 21.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 4.9 kB, which is 18% 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 21.1 kB or 78% of the original size.
Potential reduce by 7.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. To Local images are well optimized though.
Potential reduce by 247.6 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 247.6 kB or 63% of the original size.
Potential reduce by 145.2 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. Tolocal.nl needs all CSS files to be minified and compressed as it can save up to 145.2 kB or 85% of the original size.
Number of requests can be reduced by 43 (77%)
56
13
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of To Local. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.tolocal.nl
1082 ms
video-js.css
41 ms
video.js
81 ms
style.css
94 ms
styles.css
172 ms
jquery.qtip.min.css
175 ms
default.css
176 ms
rounded.css
183 ms
plugin-styles.css
184 ms
video-js.css
42 ms
jetpack.css
188 ms
jquery.js
345 ms
jquery-migrate.min.js
261 ms
iphorm.js
260 ms
swfupload.min.js
275 ms
jquery.iphorm.js
274 ms
jquery.form.min.js
280 ms
jquery.smooth-scroll.min.js
430 ms
jquery.qtip.min.js
431 ms
jquery.uniform.min.js
436 ms
jquery.infieldlabel.min.js
434 ms
rounded.js
437 ms
core.min.js
437 ms
widget.min.js
442 ms
tabs.min.js
444 ms
accordion.min.js
453 ms
superfish.js
454 ms
slides.min.jquery.js
470 ms
isotope.pkgd.min.js
508 ms
jquery.custom.js
515 ms
comment-reply.min.js
520 ms
__utm.gif
27 ms
wp-emoji-release.min.js
451 ms
Fietsers-Nederland-Large1.jpg
1004 ms
LnkedIn.png
257 ms
logo-tolocal-web2.jpg
239 ms
dots.gif
277 ms
bg-widget-title.gif
286 ms
icon-mobile-220x140.jpg
305 ms
icon-native-220x140.jpg
322 ms
icon-display-220x140.jpg
357 ms
icon-video-220x140.jpg
365 ms
icons.png
372 ms
ToLocalHomeScreen.jpg
539 ms
vjs.woff
23 ms
vjs.woff
23 ms
connect.onlinesucces.nl
263 ms
analytics.js
29 ms
collect
32 ms
file-upload-tick.png
84 ms
captcha-refresh-icon.png
96 ms
default-loading.gif
87 ms
error.png
96 ms
success.png
88 ms
input-active-bg-rep.png
93 ms
file-upload-progress-area.png
166 ms
file-progress-bar-bg.png
173 ms
file-close.png
173 ms
button-active-bg-rep.png
183 ms
tolocal.nl accessibility score
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
Links do not have a discernible name
tolocal.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
Browser errors were logged to the console
tolocal.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Tolocal.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 Tolocal.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.
tolocal.nl
Open Graph description is not detected on the main page of To Local. 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: