3.6 sec in total
426 ms
3 sec
185 ms
Visit fenris.cz now to see the best up-to-date Fenris content and also check out these interesting facts you probably never knew about fenris.cz
Fenris.cz – instalace šablon a rozšíření pro Joomla!, Wordpress a Drupal - Úvodní stránka
Visit fenris.czWe analyzed Fenris.cz page load time and found that the first response time was 426 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fenris.cz performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value10.6 s
0/100
25%
Value11.4 s
5/100
10%
Value130 ms
96/100
30%
Value0
100/100
15%
Value9.0 s
34/100
10%
426 ms
1104 ms
110 ms
210 ms
212 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 97% of them (65 requests) were addressed to the original Fenris.cz, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fenris.cz.
Page size can be reduced by 39.9 kB (9%)
429.2 kB
389.3 kB
In fact, the total size of Fenris.cz main page is 429.2 kB. 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 231.6 kB which makes up the majority of the site volume.
Potential reduce by 22.4 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 22.4 kB or 79% of the original size.
Potential reduce by 5.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. Fenris images are well optimized though.
Potential reduce by 3.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 8.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. Fenris.cz needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 23% of the original size.
Number of requests can be reduced by 47 (72%)
65
18
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fenris. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
fenris.cz
426 ms
www.fenris.cz
1104 ms
widgetkit-90bc3fac.css
110 ms
calendar.css
210 ms
front.css
212 ms
style.css
211 ms
rating.css
213 ms
prettify.css
214 ms
mootools-core.js
323 ms
core.js
313 ms
caption.js
314 ms
jquery.js
419 ms
widgetkit-1c1d88dd.js
317 ms
script.js
319 ms
rating.js
416 ms
prettify.js
417 ms
base.css
456 ms
layout.css
456 ms
menus.css
457 ms
modules.css
520 ms
tools.css
521 ms
system.css
523 ms
extensions.css
526 ms
custom.css
532 ms
blue.css
533 ms
trebuchet.css
623 ms
trebuchet.css
623 ms
trebuchet.css
624 ms
style.css
631 ms
print.css
636 ms
warp.js
639 ms
accordionmenu.js
725 ms
dropdownmenu.js
726 ms
template.js
727 ms
search.js
735 ms
lightbox.js
309 ms
mediaelement-and-player.js
313 ms
spotlight.js
394 ms
base.css
380 ms
layout.css
381 ms
menus.css
389 ms
modules.css
333 ms
tools.css
336 ms
system.css
415 ms
system.css
416 ms
system-all.css
418 ms
print.css
313 ms
toolbar.png
109 ms
menu_line_item.png
109 ms
searchbox.png
108 ms
15412418-round-paper-tag-with-folded-edge-and-colour-present-icon_ba9b14f1ebb9a811c752ff25775927a6.jpg
215 ms
buy_now_4948cd7b08413835291c07cda0385e8f.png
107 ms
logo_footer.png
108 ms
header_bg.jpg
209 ms
header.jpg
517 ms
logo_blue.png
309 ms
main.jpg
201 ms
item_links.png
202 ms
list_line.png
305 ms
module_badges.png
303 ms
module_icons.png
301 ms
stars.png
304 ms
footer.png
388 ms
totop_scroller.png
390 ms
ga.js
27 ms
searchbox_results.png
364 ms
__utm.gif
11 ms
fenris.cz 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.
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
fenris.cz 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fenris.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
![]()
CS
![]()
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fenris.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that Fenris.cz 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.
fenris.cz
Open Graph description is not detected on the main page of Fenris. 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: