11.8 sec in total
3.3 sec
8.3 sec
204 ms
Visit capitolo.hr now to see the best up-to-date Capitolo content and also check out these interesting facts you probably never knew about capitolo.hr
WebShop higijenski sustavi, prodaja, i distribucija papirnate konfekcije, sredstava za čišćenje i ostalog potrošnog materijala.
Visit capitolo.hrWe analyzed Capitolo.hr page load time and found that the first response time was 3.3 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
capitolo.hr performance score
name
value
score
weighting
Value17.0 s
0/100
10%
Value29.3 s
0/100
25%
Value28.8 s
0/100
10%
Value1,830 ms
9/100
30%
Value0.779
5/100
15%
Value29.6 s
0/100
10%
3306 ms
352 ms
27 ms
352 ms
351 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 93% of them (149 requests) were addressed to the original Capitolo.hr, 4% (6 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Capitolo.hr.
Page size can be reduced by 2.9 MB (73%)
4.1 MB
1.1 MB
In fact, the total size of Capitolo.hr main page is 4.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. 70% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 322.3 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 322.3 kB or 88% of the original size.
Potential reduce by 22.6 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. Capitolo images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 70% of the original size.
Potential reduce by 1.2 MB
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. Capitolo.hr needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 87% of the original size.
Number of requests can be reduced by 131 (89%)
148
17
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capitolo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 93 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
www.capitolo.hr
3306 ms
style-index.css
352 ms
css
27 ms
isotop-port.css
352 ms
custom.css
351 ms
owl.carousel.css
353 ms
owl.transitions.css
365 ms
shadowbox.css
471 ms
shortcode_style.css
699 ms
animate.min.css
584 ms
woocommerce.css
819 ms
style.min.css
845 ms
jquery.selectBox.css
593 ms
font-awesome.css
711 ms
prettyPhoto.css
718 ms
style.css
810 ms
frontend.css
933 ms
badges.css
834 ms
styles.css
839 ms
wpcf7-redirect-frontend.min.css
939 ms
cookie-law-info-public.css
940 ms
cookie-law-info-gdpr.css
955 ms
settings.css
1072 ms
style.css
964 ms
frontend.css
1056 ms
colorbox.css
1058 ms
yith-quick-view.css
1060 ms
style.css
1308 ms
css
19 ms
font-awesome.css
1091 ms
style.css
1180 ms
free-shipping.css
1181 ms
photoswipe.min.css
1186 ms
default-skin.min.css
1191 ms
js_composer.min.css
1578 ms
front.css
1302 ms
jquery.min.js
1418 ms
jquery-migrate.min.js
1311 ms
css
15 ms
css
13 ms
cookie-law-info-public.js
975 ms
jquery.themepunch.tools.min.js
1089 ms
jquery.themepunch.revolution.min.js
1092 ms
jquery.blockUI.min.js
1094 ms
add-to-cart.min.js
1081 ms
js.cookie.min.js
1086 ms
wc-blocks.css
978 ms
responsive.css
972 ms
woocommerce.min.js
880 ms
woocommerce-add-to-cart.js
866 ms
jquery.jqtransform.js
967 ms
jquery.jqtransform.script.js
964 ms
jquery.custom.min.js
874 ms
megnor.min.js
860 ms
carousel.min.js
856 ms
jquery.easypiechart.min.js
874 ms
custom.js
960 ms
owl.carousel.min.js
871 ms
jquery.formalize.min.js
871 ms
respond.min.js
871 ms
jquery.validate.js
857 ms
shadowbox.js
874 ms
jquery.megamenu.js
871 ms
easyResponsiveTabs.js
867 ms
jquery.treeview.js
862 ms
jquery.jscroll.min.js
853 ms
countUp.js
840 ms
doubletaptogo.js
787 ms
html5.js
863 ms
megnorloadmore.js
860 ms
photoswipe.min.js
855 ms
photoswipe-ui-default.min.js
743 ms
front.min.js
860 ms
jquery.selectBox.min.js
786 ms
jquery.prettyPhoto.min.js
854 ms
jquery.yith-wcwl.min.js
751 ms
frontend.js
743 ms
colcade.js
737 ms
index.js
891 ms
index.js
929 ms
wpcf7r-fe.js
817 ms
sourcebuster.min.js
811 ms
order-attribution.min.js
809 ms
wp-polyfill-inert.min.js
809 ms
regenerator-runtime.min.js
835 ms
wp-polyfill.min.js
862 ms
react.min.js
817 ms
hooks.min.js
812 ms
deprecated.min.js
812 ms
dom.min.js
809 ms
react-dom.min.js
840 ms
escape-html.min.js
902 ms
element.min.js
810 ms
is-shallow-equal.min.js
807 ms
i18n.min.js
809 ms
keycodes.min.js
810 ms
priority-queue.min.js
843 ms
compose.min.js
897 ms
private-apis.min.js
813 ms
redux-routine.min.js
812 ms
data.min.js
816 ms
lodash.min.js
817 ms
wc-blocks-registry.js
849 ms
url.min.js
892 ms
api-fetch.min.js
815 ms
wc-settings.js
813 ms
data-controls.min.js
816 ms
html-entities.min.js
817 ms
notices.min.js
813 ms
wc-blocks-middleware.js
814 ms
wc-blocks-data.js
945 ms
dom-ready.min.js
813 ms
a11y.min.js
815 ms
primitives.min.js
791 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
129 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
130 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
169 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
181 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
180 ms
responsive.css
715 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQbMZhKg.ttf
52 ms
warning.min.js
751 ms
blocks-components.js
751 ms
blocks-checkout.js
751 ms
order-attribution-blocks.min.js
753 ms
frontend.min.js
798 ms
woocompare.min.js
822 ms
jquery.colorbox-min.js
744 ms
frontend.min.js
746 ms
functions.js
747 ms
navigation.js
748 ms
isotope.pkgd.min.js
814 ms
waypoints.min.js
817 ms
smush-lazy-load.min.js
747 ms
js_composer_front.min.js
752 ms
underscore.min.js
764 ms
wp-util.min.js
765 ms
add-to-cart-variation.min.js
821 ms
jquery.zoom.min.js
812 ms
single-product.min.js
747 ms
fontawesome-webfont.woff
825 ms
fontawesome-webfont.woff
824 ms
star.woff
822 ms
star.woff
871 ms
body-bg.png
831 ms
sprite.png
756 ms
toilet-paper-627032_1920.jpg
864 ms
sprite.png
754 ms
CAPITOLO_logo_75_w.png
304 ms
cube-74x82_t.png
335 ms
Paket-74x82_t.jpg
358 ms
rhutten-logo-74x82_t.png
378 ms
Folije-i-vre%C4%87ice-74x82_t.png
375 ms
revolution.extension.slideanims.min.js
283 ms
revolution.extension.actions.min.js
334 ms
revolution.extension.layeranimation.min.js
355 ms
revolution.extension.kenburn.min.js
357 ms
revolution.extension.navigation.min.js
376 ms
revolution.extension.parallax.min.js
373 ms
jlxdhqbbs05358ksd4hfceepmo4e30zi.js
164 ms
capitolo.hr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s are not contained by their required parent element
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
capitolo.hr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
capitolo.hr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
EN
HR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capitolo.hr 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 Croatian language. Our system also found out that Capitolo.hr 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.
capitolo.hr
Open Graph data is detected on the main page of Capitolo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: