4.9 sec in total
228 ms
4.2 sec
474 ms
Visit 4story.cz now to see the best up-to-date 4Story content and also check out these interesting facts you probably never knew about 4story.cz
Visit 4story.czWe analyzed 4story.cz page load time and found that the first response time was 228 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
4story.cz performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value30.5 s
0/100
25%
Value13.2 s
2/100
10%
Value1,760 ms
10/100
30%
Value0.221
56/100
15%
Value25.5 s
0/100
10%
228 ms
363 ms
2439 ms
2465 ms
2517 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 4story.cz, 25% (22 requests) were made to Gf2.geo.gfsrv.net and 24% (21 requests) were made to Gf3.geo.gfsrv.net. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Gf2.geo.gfsrv.net.
Page size can be reduced by 4.7 MB (55%)
8.5 MB
3.8 MB
In fact, the total size of 4story.cz main page is 8.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. 55% of websites need less resources to load. Javascripts take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 103.2 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 23.5 kB, which is 19% 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 103.2 kB or 83% of the original size.
Potential reduce by 3.1 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. 4Story images are well optimized though.
Potential reduce by 4.3 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 4.3 MB or 81% of the original size.
Potential reduce by 309.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. 4story.cz needs all CSS files to be minified and compressed as it can save up to 309.2 kB or 81% of the original size.
Number of requests can be reduced by 39 (48%)
81
42
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4Story. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
4story.cz
228 ms
cz.4story.gameforge.com
363 ms
f6763cdbc2ed563e6dabdfbcd9e53a.css
2439 ms
38ef77dbb86fe1861565522048757b.css
2465 ms
30325903cf4267fd4ee6887940f667.css
2517 ms
eeaead4680de9f26323b889fe76e4e.css
2497 ms
94e9c988775d4d9602df27aaa69c04.css
2424 ms
d55973f091809f12086605c680624f.js
2487 ms
32296d48ee3740c4f071969d20d006.js
2562 ms
74a2472b07741e6900b40d529efc36.js
2436 ms
a7e7115215785502490da6c890ee95.js
2416 ms
94da4a34cdb09b074ea89e4396df7e.js
2544 ms
20407a47f5b7d7c3f695cf2ca6327b.js
2435 ms
a560009b332c49b79a445b0bd29860.js
2493 ms
d125e4b15d947ef5084affffc7b85d.js
2412 ms
356416b592bd7ee5c8539905d40ce7.js
2491 ms
8d3acd9fa6dbc3b1d17f16c7936aac.js
2492 ms
f33f613c053ffb5dba80074dc1d59e.js
2413 ms
b11ba3a629b2afb593b71eee16c9cf.js
2532 ms
b3ba493bd716fd33b9ff54223c7895.js
2441 ms
7116a2b08d6e90406f63724abd7b44.js
2411 ms
c7a759afa23c3ae3bae667b596e9d1.js
2410 ms
c290a391c0d68ef105015f0a0bb098.js
2461 ms
f43ec99012268cc69d2a8b66f04917.js
2966 ms
2afbea55e85fae57c4ed5977918cf6.js
2461 ms
eccf4b6441b7bbdd817a1dd9ba808f.js
2461 ms
functions.js
227 ms
59ad78df222be12ef3c12bf518a47d.jpg
215 ms
ebf2dabe3cd1d8e0c225c8b8ecb085.png
52 ms
d61df2a01926955510b875f6b1be9d.jpg
111 ms
f410a3e2c90af68bdec24c0fa732aa.png
125 ms
a1bf3e2ba87b3b6193ce7e0bc44903.png
27 ms
15d414403178270294ffb516e06e25.jpg
55 ms
61e2f779bf1e832e24df079a927e99.png
210 ms
3ae9063a7415d0ee62703129786fa5.png
124 ms
7dfe2628b2a2370fe0243be9bcc93d.jpg
99 ms
ba7a680739499d35dc3d8a8a1aef2a.png
99 ms
c0edcb00625bf9bf274d5000d798db.png
31 ms
0934998a5191a71538ccdc2b61b63c.jpg
31 ms
99cfaa6b52934834f249cd64d5bec9.png
30 ms
bb946fbdf7ca356b2b3e3154d5bf21.jpg
58 ms
97342be639b3ad38305dbb0181a40b.png
32 ms
e0d5cf79041f8f6107d2ba197374ff.gif
55 ms
5a96a565163170ba492430fa1e11ef.png
54 ms
9747664f9e03680c70b35367eb1fc7.jpg
145 ms
59351a908d3c5ccf1dc925c9db5092.jpg
148 ms
598484d8e8c14086232ac5db1d8240.jpg
96 ms
23c707acfb5532ed7608bbee4f24fb.png
96 ms
6a7805684d88cddd0e5e5f395e5572.png
124 ms
4f4b3a18939fe179d7792e145ea15c.jpg
211 ms
ajs.php
195 ms
0aadc758a4498e33a8d89b0b0dde00.png
28 ms
1854da5778e3269525e94e185a8128.png
73 ms
e33da11dfe7f3e0c511125dbdd95ee.png
30 ms
KzroQJRM1tg
121 ms
www-embed-player-vflRGs1ko.css
75 ms
www-embed-player.js
98 ms
a192d3f34423ed43b9e072f3136e79.png
55 ms
7e107d96490a49c772978f70910e3e.jpg
27 ms
lg.php
372 ms
de3d5a926f41bd1838ca3d7f2df673.jpg
27 ms
64d3e0be4f9ad51ec0c8e66ad2cf65.jpg
28 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
48 ms
ad_status.js
28 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
300 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
312 ms
ga.js
39 ms
Simple
353 ms
atrk.js
52 ms
2d40928b486ee1ece704628d8c9e20.png
29 ms
24c9a6c60ffe7e0a60cc6ed55bdf6f.png
49 ms
0fa15cfe12b31b8e79f9598f106bfd.png
47 ms
al.php
196 ms
__utm.gif
14 ms
atrk.gif
28 ms
test.png
438 ms
75c446aafdfbf67356490c997806e3.png
115 ms
6cbace8ebf36bce41afd56ad0fbe49.png
114 ms
7d7f425be8ac8ec7604b1ab42ed35b.png
75 ms
lg.php
192 ms
bdd46ce1513784e3c8bbca3d787e68.jpg
33 ms
5c1a1eac437599dea31469ff0ebfbf.jpg
28 ms
conversion.js
16 ms
__utm.gif
11 ms
34 ms
37 ms
19 ms
4story.cz 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
4story.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
Missing source maps for large first-party JavaScript
4story.cz 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
CS
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4story.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 4story.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.
4story.cz
Open Graph description is not detected on the main page of 4Story. 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: