9.4 sec in total
460 ms
6.1 sec
2.9 sec
Click here to check amazing Gerkand content. Otherwise, check out these important facts you probably never knew about gerkand.com
Cast iron wood burning fireplace inserts, wood and pellet stoves, cast iron home and professional BBQ grill by the producer Gerkand Ltd.
Visit gerkand.comWe analyzed Gerkand.com page load time and found that the first response time was 460 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
gerkand.com performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value11.4 s
0/100
25%
Value18.0 s
0/100
10%
Value260 ms
83/100
30%
Value0.003
100/100
15%
Value16.2 s
5/100
10%
460 ms
2143 ms
453 ms
606 ms
27 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 72% of them (67 requests) were addressed to the original Gerkand.com, 24% (22 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Gerkand.com.
Page size can be reduced by 1.5 MB (59%)
2.5 MB
1.0 MB
In fact, the total size of Gerkand.com main page is 2.5 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 883.2 kB which makes up the majority of the site volume.
Potential reduce by 173.9 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 173.9 kB or 85% of the original size.
Potential reduce by 843 B
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. Gerkand images are well optimized though.
Potential reduce by 619.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 619.1 kB or 70% of the original size.
Potential reduce by 697.2 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. Gerkand.com needs all CSS files to be minified and compressed as it can save up to 697.2 kB or 87% of the original size.
Number of requests can be reduced by 47 (70%)
67
20
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gerkand. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
gerkand.com
460 ms
2143 ms
wp-emoji-release.min.js
453 ms
style.min.css
606 ms
css
27 ms
style.min.css
579 ms
vendors-style.css
350 ms
style.css
846 ms
woocommerce-layout.min.css
582 ms
woocommerce.min.css
703 ms
astra-addon-5f9032192b28d1-17629931.css
482 ms
elementor-icons.min.css
392 ms
animations.min.css
455 ms
frontend-legacy.min.css
459 ms
frontend.min.css
648 ms
post-5379.css
512 ms
font-awesome.min.css
571 ms
post-1848.css
692 ms
style.css
576 ms
cookieconsent.min.css
634 ms
css
19 ms
jquery.js
801 ms
style.min.js
588 ms
jquery.blockUI.min.js
608 ms
add-to-cart.min.js
637 ms
js.cookie.min.js
651 ms
woocommerce.min.js
812 ms
jquery.cookie.min.js
811 ms
Cart.min.js
813 ms
imagesloaded.min.js
822 ms
astra-addon-5f9032192c6e90-90999535.js
821 ms
single-product-ajax-cart.min.js
820 ms
cookieconsent.min.js
821 ms
postscribe.min.js
820 ms
complianz.min.js
923 ms
wp-embed.min.js
946 ms
underscore.min.js
944 ms
wp-util.min.js
945 ms
add-to-cart-variation.min.js
943 ms
jquery.flexslider.min.js
943 ms
frontend-modules.min.js
1047 ms
position.min.js
1064 ms
dialog.min.js
919 ms
waypoints.min.js
851 ms
swiper.min.js
1077 ms
share-link.min.js
829 ms
frontend.min.js
900 ms
frontend.min.js
830 ms
cropped-gerkand-fireplaces-logo-3-170x60.png
436 ms
Front-page-1-1.jpg
437 ms
scroll.png
446 ms
white-brick-background.jpg
544 ms
Fireplace-Maxi-1-Aero-1.jpg
550 ms
Fireplace-cladding-by-Gerkand.jpg
553 ms
home.fireplace.interior.jpg
557 ms
Pellet-stove-Kayla-1.jpg
749 ms
BBQ-Locomotive-1.jpg
765 ms
Maxi-2-Fireplace-insert-1.jpg
780 ms
%D0%BA%D0%B0%D0%BC%D0%B8%D0%BD%D0%B8-%D0%B3%D0%B5%D1%80%D0%BA%D0%B0%D0%BD%D0%B4-%D0%B2%D0%B8%D1%81%D0%BE%D0%BA%D0%BE%D0%BA%D0%B0%D1%87%D0%B5%D1%81%D1%82%D0%B2%D0%B5%D0%BD%D0%B8-%D0%BC%D0%B0%D1%82%D0%B5%D1%80%D0%B8%D0%B0%D0%BB%D0%B8.png
765 ms
%D0%9A%D0%B0%D0%BC%D0%B8%D0%BD%D0%B8-%D1%81-%D0%B5%D0%BB%D0%B5%D0%B3%D0%B0%D0%BD%D1%82%D0%B5%D0%BD-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD.png
765 ms
%D0%9A%D0%B0%D0%BC%D0%B8%D0%BD%D0%B8-%D0%93%D0%B5%D1%80%D0%BA%D0%B0%D0%BD%D0%B4-%D0%9A%D0%9F%D0%94-%D0%BD%D0%B0%D0%B4-70-%D0%BF%D0%BE-%D0%BD%D0%B8%D1%81%D1%8A%D0%BA-%D1%80%D0%B0%D0%B7%D1%85%D0%BE%D0%B4.png
766 ms
%D0%91%D0%B5%D0%B7%D0%BE%D0%BF%D0%B0%D1%81%D0%BD%D0%B0-%D1%83%D0%BF%D0%BE%D1%82%D1%80%D0%B5%D0%B1%D0%B0-%D0%BD%D0%B0-%D0%BA%D0%B0%D0%BC%D0%B8%D0%BD%D0%B8-%D0%93%D0%B5%D1%80%D0%BA%D0%B0%D0%BD%D0%B4.png
693 ms
%D0%95%D0%B2%D1%80%D0%BE%D0%BF%D0%B5%D0%B9%D1%81%D0%BA%D0%B8-%D0%BF%D1%80%D0%BE%D0%B8%D0%B7%D0%B2%D0%BE%D0%B4%D0%B8%D1%82%D0%B5%D0%BB-%D0%BD%D0%B0-%D0%BA%D0%B0%D0%BC%D0%B8%D0%BD%D0%B8-%D0%BB%D0%B5%D1%81%D0%BD%D0%B0-%D0%B5%D0%BA%D1%81%D0%BF%D0%BB%D0%BE%D0%B0%D1%82%D0%B0%D1%86%D0%B8%D1%8F.png
695 ms
white-brick-background.jpg
711 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
113 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
132 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
132 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
132 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
131 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
131 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
132 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
165 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
165 ms
OpNJno4VhNfK-RgpwWWxli1VXg.ttf
197 ms
astra.woff
720 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuXMQg.ttf
164 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMQg.ttf
165 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf
164 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWAosBO5Xk.ttf
197 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf
197 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUyosBO5Xk.ttf
196 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyo8BO5Xk.ttf
196 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVspcBO5Xk.ttf
196 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf
198 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUypcBO5Xk.ttf
199 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUbpcBO5Xk.ttf
198 ms
zYXgKVElMYYaJe8bpLHnCwDKhdHeEA.ttf
196 ms
fontawesome-webfont.woff
845 ms
embed
590 ms
1134 ms
frontend-msie.min.css
151 ms
js
77 ms
woocommerce-smallscreen.min.css
125 ms
gerkand.com 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.
gerkand.com 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
gerkand.com 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gerkand.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Gerkand.com 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.
gerkand.com
Open Graph data is detected on the main page of Gerkand. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: