7.1 sec in total
312 ms
6.5 sec
255 ms
Click here to check amazing Code 92 content. Otherwise, check out these important facts you probably never knew about code92.nl
Online Portfolio of Emile Nijssen
Visit code92.nlWe analyzed Code92.nl page load time and found that the first response time was 312 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
code92.nl performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value2.3 s
93/100
25%
Value2.3 s
99/100
10%
Value110 ms
97/100
30%
Value0.018
100/100
15%
Value3.4 s
93/100
10%
312 ms
3620 ms
369 ms
648 ms
196 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Code92.nl, 94% (45 requests) were made to Emilenijssen.nl and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Emilenijssen.nl.
Page size can be reduced by 223.5 kB (13%)
1.7 MB
1.5 MB
In fact, the total size of Code92.nl main page is 1.7 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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 61.4 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 8.8 kB, which is 12% 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 61.4 kB or 85% of the original size.
Potential reduce by 56.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. Code 92 images are well optimized though.
Potential reduce by 92.1 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 92.1 kB or 61% of the original size.
Potential reduce by 13.7 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. Code92.nl needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 84% of the original size.
Number of requests can be reduced by 4 (9%)
44
40
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Code 92. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
code92.nl
312 ms
emilenijssen.nl
3620 ms
style.css
369 ms
jquery.js
648 ms
jquery.mousewheel.js
196 ms
iscroll.js
465 ms
emilenijssen.nl.js
291 ms
photo.jpg
811 ms
pattern.png
188 ms
home.png
189 ms
cursor-drag-open.png
163 ms
preview-bg.png
164 ms
ga.js
22 ms
timthumb.php
407 ms
timthumb.php
817 ms
timthumb.php
829 ms
timthumb.php
960 ms
timthumb.php
278 ms
timthumb.php
903 ms
timthumb.php
623 ms
timthumb.php
749 ms
timthumb.php
900 ms
timthumb.php
904 ms
timthumb.php
1019 ms
timthumb.php
945 ms
timthumb.php
995 ms
timthumb.php
1006 ms
timthumb.php
1022 ms
timthumb.php
1061 ms
timthumb.php
1169 ms
timthumb.php
1103 ms
timthumb.php
1124 ms
timthumb.php
1216 ms
timthumb.php
1167 ms
timthumb.php
1175 ms
timthumb.php
1227 ms
timthumb.php
1228 ms
timthumb.php
1275 ms
timthumb.php
1750 ms
timthumb.php
1288 ms
timthumb.php
1318 ms
timthumb.php
1331 ms
timthumb.php
1330 ms
timthumb.php
1399 ms
__utm.gif
12 ms
universltstdcn.woff
1275 ms
universltstdboldcn.woff
1302 ms
timthumb.php
1298 ms
code92.nl accessibility score
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
code92.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
code92.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Code92.nl can be misinterpreted by Google and other search engines. Our service has detected that English 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 Code92.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.
code92.nl
Open Graph description is not detected on the main page of Code 92. 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: