2.7 sec in total
488 ms
2.1 sec
125 ms
Click here to check amazing Pirana content. Otherwise, check out these important facts you probably never knew about pirana.be
Visit pirana.beWe analyzed Pirana.be page load time and found that the first response time was 488 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.
pirana.be performance score
name
value
score
weighting
Value1.1 s
100/100
10%
Value1.7 s
99/100
25%
Value1.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.1 s
100/100
10%
488 ms
535 ms
183 ms
190 ms
193 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 95% of them (52 requests) were addressed to the original Pirana.be, 2% (1 request) were made to Netdna.bootstrapcdn.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (839 ms) belongs to the original domain Pirana.be.
Page size can be reduced by 1.1 MB (84%)
1.3 MB
199.9 kB
In fact, the total size of Pirana.be main page is 1.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. 40% of websites need less resources to load. Images take 777.5 kB which makes up the majority of the site volume.
Potential reduce by 17.0 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 3.2 kB, which is 14% 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 17.0 kB or 77% of the original size.
Potential reduce by 695.0 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, Pirana needs image optimization as it can save up to 695.0 kB or 89% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 183.8 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 183.8 kB or 71% of the original size.
Potential reduce by 191.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. Pirana.be needs all CSS files to be minified and compressed as it can save up to 191.7 kB or 84% of the original size.
Number of requests can be reduced by 33 (63%)
52
19
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pirana. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
488 ms
bootstrap.css
535 ms
default.css
183 ms
template.css
190 ms
touch.gallery.css
193 ms
komento.css
184 ms
magnific-popup.css
185 ms
responsive.css
288 ms
font-awesome.css
9 ms
css
24 ms
module_default.css
326 ms
superfish.css
285 ms
superfish-navbar.css
295 ms
superfish-vertical.css
298 ms
template.css
396 ms
ogb-lib.js
390 ms
ogb.js
392 ms
jquery.min.js
658 ms
jquery-noconflict.js
411 ms
jquery-migrate.min.js
479 ms
caption.js
502 ms
jquery.mobile.customized.min.js
618 ms
jquery.easing.1.3.js
508 ms
bootstrap.min.js
688 ms
jquery.isotope.min.js
608 ms
jquery.magnific-popup.js
780 ms
ios-orientationchange-fix.js
617 ms
desktop-mobile.js
697 ms
jquery.BlackAndWhite.min.js
718 ms
scripts.js
724 ms
acymailing_module.js
758 ms
superfish.min.js
756 ms
jquery.mobilemenu.js
791 ms
hoverIntent.js
820 ms
supersubs.js
829 ms
sftouchscreen.js
839 ms
bg.gif
104 ms
bg_slider.gif
108 ms
logo_bg.png
200 ms
logo.png
301 ms
nl_be.gif
110 ms
en.gif
139 ms
icon-1.png
273 ms
icon-1-active.png
277 ms
icon-2.png
364 ms
icon-2-active.png
298 ms
icon-3.png
358 ms
icon-3-active.png
359 ms
icon-4.png
447 ms
icon-4-active.png
458 ms
icon-about.png
385 ms
search_bg.png
430 ms
search_button.png
414 ms
up-arrow.png
409 ms
QmTOgNNWM9ly3K3B2X29HL3hpw3pgy2gAi-Ip7WPMi0.woff
5 ms
pirana.be 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
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
Image elements do not have [alt] attributes
pirana.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
pirana.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pirana.be 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 Pirana.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.
pirana.be
Open Graph description is not detected on the main page of Pirana. 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: