2.8 sec in total
636 ms
2 sec
167 ms
Welcome to edwinvandegraaf.nl homepage info - get ready to check Edwin Van De Graaf best content right away, or after learning these important things about edwinvandegraaf.nl
Fotograaf Doetinchem. Professionele en toegankelijke fotograaf voor commercieel beeld, portretten en reportages (ook huwelijk) werkt vanuit Doetinchem.
Visit edwinvandegraaf.nlWe analyzed Edwinvandegraaf.nl page load time and found that the first response time was 636 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
edwinvandegraaf.nl performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value9.0 s
1/100
25%
Value10.2 s
8/100
10%
Value30 ms
100/100
30%
Value0.017
100/100
15%
Value6.4 s
59/100
10%
636 ms
41 ms
88 ms
173 ms
262 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 61% of them (23 requests) were addressed to the original Edwinvandegraaf.nl, 8% (3 requests) were made to Facebook.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (636 ms) belongs to the original domain Edwinvandegraaf.nl.
Page size can be reduced by 354.2 kB (72%)
492.3 kB
138.1 kB
In fact, the total size of Edwinvandegraaf.nl main page is 492.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 342.3 kB which makes up the majority of the site volume.
Potential reduce by 20.5 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 20.5 kB or 75% of the original size.
Potential reduce by 7.3 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, Edwin Van De Graaf needs image optimization as it can save up to 7.3 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 239.2 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 239.2 kB or 70% of the original size.
Potential reduce by 87.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. Edwinvandegraaf.nl needs all CSS files to be minified and compressed as it can save up to 87.1 kB or 85% of the original size.
Number of requests can be reduced by 25 (74%)
34
9
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edwin Van De Graaf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.edwinvandegraaf.nl
636 ms
css
41 ms
ggskin.css
88 ms
prettyPhoto.css
173 ms
style.css
262 ms
cssLoader.php
411 ms
styles-32.min.css
174 ms
swfobject.js
174 ms
jquery.js
282 ms
jquery-migrate.min.js
255 ms
main.js
346 ms
grid-gallery.js
345 ms
platform.js
98 ms
wp-embed.min.js
338 ms
comment-reply.min.js
342 ms
wp-emoji-release.min.js
321 ms
gtm.js
112 ms
analytics.js
20 ms
fbds.js
38 ms
noise.png
109 ms
logo-fotograaf-groningen-edwinvandegraaf.jpg
115 ms
youtube.png
110 ms
facebook.png
113 ms
vimeo.png
111 ms
googleplus.png
112 ms
pinterest.png
171 ms
ajax-loader.gif
172 ms
G0XvmuebhPCfCq4YdUpRgALUuEpTyoUstqEm5AMlJo4.ttf
17 ms
0XxGQsSc1g4rdRdjJKZrNMDdSZkkecOE1hvV7ZHvhyU.ttf
18 ms
collect
75 ms
sdk.js
78 ms
collect
70 ms
drop-arrow.png
86 ms
48 ms
36 ms
xd_arbiter.php
79 ms
xd_arbiter.php
133 ms
15 ms
edwinvandegraaf.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.
edwinvandegraaf.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
edwinvandegraaf.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
NL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edwinvandegraaf.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Edwinvandegraaf.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.
edwinvandegraaf.nl
Open Graph data is detected on the main page of Edwin Van De Graaf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: