5.3 sec in total
1.5 sec
3.6 sec
180 ms
Click here to check amazing Canary Pete content. Otherwise, check out these important facts you probably never knew about canarypete.be
Canary Pete Images - Cartoons & Illustraties. Officiële website van cartoonist Canary Pete.
Visit canarypete.beWe analyzed Canarypete.be page load time and found that the first response time was 1.5 sec 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.
canarypete.be performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value9.9 s
0/100
25%
Value10.1 s
9/100
10%
Value210 ms
89/100
30%
Value0
100/100
15%
Value9.1 s
33/100
10%
1526 ms
254 ms
337 ms
416 ms
420 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 93% of them (42 requests) were addressed to the original Canarypete.be, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Dv-webdesign.be. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Canarypete.be.
Page size can be reduced by 657.3 kB (58%)
1.1 MB
483.8 kB
In fact, the total size of Canarypete.be main page is 1.1 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. 25% of websites need less resources to load. Javascripts take 609.3 kB which makes up the majority of the site volume.
Potential reduce by 15.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 2.9 kB, which is 15% 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 15.1 kB or 78% of the original size.
Potential reduce by 8.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. Canary Pete images are well optimized though.
Potential reduce by 427.0 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 427.0 kB or 70% of the original size.
Potential reduce by 206.3 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. Canarypete.be needs all CSS files to be minified and compressed as it can save up to 206.3 kB or 81% of the original size.
Number of requests can be reduced by 32 (76%)
42
10
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Canary Pete. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
canarypete.be
1526 ms
calendar.css
254 ms
front.css
337 ms
rokbox.css
416 ms
master.css
420 ms
grid-12-responsive.css
254 ms
gantry-core.css
243 ms
joomla-core.css
488 ms
main-light.css
502 ms
utilities.css
335 ms
typography.css
504 ms
template.css
417 ms
template-opera.css
540 ms
thirdparty-k2.css
596 ms
thirdparty-k2-light.css
504 ms
mediaqueries.css
569 ms
demo-styles.css
594 ms
mycustomstyle.css
583 ms
style.css
584 ms
jquery.min.js
871 ms
jquery-noconflict.js
575 ms
jquery-migrate.min.js
589 ms
caption.js
604 ms
script.js
681 ms
mootools-core.js
846 ms
core.js
659 ms
mootools-more.js
1242 ms
rokbox.js
930 ms
gantry-totop.js
740 ms
browser-engines.js
763 ms
rokmediaqueries.js
823 ms
modules-height.js
845 ms
load-transition.js
904 ms
default.js
1010 ms
analytics.js
52 ms
dvwebdesign-dh.png
795 ms
paper2.jpg
367 ms
CanaryPeteImagesText.png
85 ms
Karikatuur.png
768 ms
fp-footer-icon3.png
83 ms
CartoonNodig.png
342 ms
sprocket-headlines.png
84 ms
dc64fc9ec3eef88ab5d3628758cc80e4.jpg
327 ms
loading.gif
165 ms
collect
11 ms
canarypete.be accessibility score
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
canarypete.be 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
canarypete.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Canarypete.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Dutch language. Our system also found out that Canarypete.be 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.
canarypete.be
Open Graph description is not detected on the main page of Canary Pete. 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: