4 sec in total
251 ms
3.3 sec
431 ms
Click here to check amazing Proximity content. Otherwise, check out these important facts you probably never knew about proximity.nl
Visit proximity.nlWe analyzed Proximity.nl page load time and found that the first response time was 251 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.
proximity.nl performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value4.8 s
30/100
25%
Value5.1 s
62/100
10%
Value520 ms
56/100
30%
Value0.193
64/100
15%
Value5.6 s
69/100
10%
251 ms
1386 ms
62 ms
156 ms
187 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Proximity.nl, 80% (57 requests) were made to Fhv.bbdo.nl and 11% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Fhv.bbdo.nl.
Page size can be reduced by 1.6 MB (69%)
2.3 MB
726.9 kB
In fact, the total size of Proximity.nl main page is 2.3 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. 70% of websites need less resources to load. Javascripts take 943.2 kB which makes up the majority of the site volume.
Potential reduce by 77.9 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 77.9 kB or 83% of the original size.
Potential reduce by 16.7 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. Proximity images are well optimized though.
Potential reduce by 721.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 721.7 kB or 77% of the original size.
Potential reduce by 782.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. Proximity.nl needs all CSS files to be minified and compressed as it can save up to 782.1 kB or 87% of the original size.
Number of requests can be reduced by 37 (67%)
55
18
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Proximity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
proximity.nl
251 ms
fhv.bbdo.nl
1386 ms
webfont.js
62 ms
wp-emoji-release.min.js
156 ms
styles.css
187 ms
woocommerce-layout.css
175 ms
woocommerce.css
197 ms
mediaelementplayer.min.css
202 ms
wp-mediaelement.css
205 ms
rgs.css
237 ms
font-awesome.min.css
259 ms
style.css
457 ms
prettyPhoto.css
279 ms
responsive.css
364 ms
css
66 ms
woocommerce.css
286 ms
ascend.css
329 ms
jquery.js
431 ms
jquery-migrate.min.js
371 ms
add-to-cart.min.js
371 ms
woocommerce-add-to-cart.js
416 ms
modernizr.js
512 ms
ProgressCircle.js
511 ms
jquery.vc_chart.js
540 ms
css
23 ms
jquery.form.min.js
494 ms
scripts.js
508 ms
jquery.blockUI.min.js
509 ms
woocommerce.min.js
510 ms
jquery.cookie.min.js
510 ms
cart-fragments.min.js
511 ms
prettyPhoto.js
621 ms
isotope.min.js
621 ms
superfish.js
625 ms
init.js
832 ms
infinitescroll.js
625 ms
mediaelement-and-player.min.js
626 ms
wp-mediaelement.js
664 ms
wp-embed.min.js
663 ms
logo-dark.png
177 ms
logo-dark-retina.png
183 ms
fonk_astrid-500x500.jpg
278 ms
rbg_square.png
232 ms
Screen-Shot-2016-01-27-at-16.51.56-500x500.jpg
314 ms
Ernst-JanSmids-1.jpg
256 ms
save_the_date_1x1.jpg
642 ms
undercon_square.jpg
642 ms
Untold01b-500x500.jpg
641 ms
bbdo_small.jpg
643 ms
whatsapp-500x500.jpg
643 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
56 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
128 ms
OpenSans-Regular-webfont.woff
640 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
128 ms
OpenSans-Light-webfont.woff
640 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
56 ms
MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff
128 ms
OpenSans-Semibold-webfont.woff
639 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
128 ms
OpenSansBold-webfont.woff
642 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
124 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
124 ms
analytics.js
54 ms
fhv.bbdo.nl
1057 ms
quote.png
630 ms
fontawesome-webfont.svg
642 ms
icomoon.woff
542 ms
collect
48 ms
fhv.bbdo.nl
446 ms
fontawesome-webfont.woff
170 ms
woocommerce-smallscreen.css
87 ms
proximity.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
<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.
proximity.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
proximity.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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proximity.nl can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Proximity.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.
proximity.nl
Open Graph description is not detected on the main page of Proximity. 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: