6.3 sec in total
1.6 sec
4.1 sec
667 ms
Click here to check amazing Campai content. Otherwise, check out these important facts you probably never knew about campai.nl
ICT beheer of IT project uitbesteden? Met 20 specialisten ontzorgt Campai MKB organisaties op ICT gebied. Wij maken graag kennis met jou!
Visit campai.nlWe analyzed Campai.nl page load time and found that the first response time was 1.6 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
campai.nl performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value6.2 s
11/100
25%
Value4.9 s
65/100
10%
Value450 ms
63/100
30%
Value0.074
95/100
15%
Value11.3 s
19/100
10%
1556 ms
171 ms
247 ms
166 ms
167 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 76% of them (72 requests) were addressed to the original Campai.nl, 13% (12 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Campai.nl.
Page size can be reduced by 1.1 MB (60%)
1.8 MB
743.2 kB
In fact, the total size of Campai.nl main page is 1.8 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. CSS take 648.2 kB which makes up the majority of the site volume.
Potential reduce by 117.8 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 117.8 kB or 86% of the original size.
Potential reduce by 34.4 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. Campai images are well optimized though.
Potential reduce by 392.5 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 392.5 kB or 71% of the original size.
Potential reduce by 551.0 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. Campai.nl needs all CSS files to be minified and compressed as it can save up to 551.0 kB or 85% of the original size.
Number of requests can be reduced by 47 (60%)
78
31
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Campai. 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 from 19 to 1 for CSS and as a result speed up the page load time.
www.campai.nl
1556 ms
language-selector.css
171 ms
dashicons.min.css
247 ms
thickbox.css
166 ms
styles.css
167 ms
custom-404-pro-public.css
190 ms
css
23 ms
style.css
190 ms
frontend.css
246 ms
css
35 ms
style.css
247 ms
app.css
254 ms
shortcodes.css
261 ms
form-themes.min.css
264 ms
shortcodes_responsive.css
325 ms
magnific_popup.css
325 ms
jquery.js
411 ms
jquery-migrate.min.js
340 ms
custom-404-pro-public.js
346 ms
conversion.js
14 ms
thickbox.js
278 ms
frontend-builder-global-functions.js
331 ms
jquery.form.min.js
331 ms
scripts.js
353 ms
idle-timer.min.js
358 ms
custom.js
365 ms
748192.js
119 ms
comment-reply.min.js
411 ms
jquery.mobile.custom.min.js
411 ms
custom.js
419 ms
jquery.fitvids.js
440 ms
waypoints.min.js
444 ms
jquery.magnific-popup.js
452 ms
frontend-builder-scripts.js
495 ms
wp-embed.min.js
491 ms
sitepress.js
498 ms
salvattore.min.js
525 ms
lib.core.js
529 ms
lib.view.js
540 ms
client.js
570 ms
client.js
573 ms
tag.item.js
500 ms
tag.ui.js
532 ms
handler.image.js
515 ms
wp-emoji-release.min.js
517 ms
style.css
664 ms
analytics.js
117 ms
campai-logo.png
110 ms
managed-ict-zoetermeer.jpg
573 ms
arrow.png
104 ms
one-partner1.png
109 ms
fast1.png
108 ms
price1.png
105 ms
knowledge1.png
199 ms
referentie-tenholternoordam-logo.png
259 ms
referentie-vliegtickets-logo.png
299 ms
referentie-c-job-logo.png
254 ms
RederijGroen.png
299 ms
Microsoft-400x284.jpg
258 ms
Datto.jpg
299 ms
Veeam-400x284.jpg
571 ms
zarafa-400x284.jpg
569 ms
hp-business-partner-400x284.jpg
571 ms
kpn-400x284.jpg
572 ms
Acronis-400x284.jpg
573 ms
vmware-400x284.jpg
574 ms
cisco-400x284.jpg
574 ms
linux-400x284.jpg
575 ms
Filterworks-400x284.jpg
575 ms
crypto-ransomware-stages-240x260.png
638 ms
AP-240x114.png
576 ms
104 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
97 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
101 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
102 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
103 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
106 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
104 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
105 ms
ETmodules_v2_4.ttf
524 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
103 ms
PRmiXeptR36kaC0GEAetxvqEJM-AK1nFUafhVdytxUY.ttf
112 ms
PRmiXeptR36kaC0GEAetxmYImPRL1w80NlYTQ8LOqf4.ttf
112 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
116 ms
PRmiXeptR36kaC0GEAetxk7Gbs5Oj9RrfpUUQRHsz5w.ttf
116 ms
ETmonarch_2.ttf
497 ms
collect
77 ms
__ptq.gif
39 ms
collect
103 ms
96 ms
style.css
89 ms
css
44 ms
style.css
83 ms
loadingAnimation.gif
105 ms
ajax-loader.gif
103 ms
campai.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.
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
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.
campai.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
campai.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
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 Campai.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 Campai.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.
campai.nl
Open Graph data is detected on the main page of Campai. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: