71.8 sec in total
471 ms
52.1 sec
19.3 sec
Visit 4story.es now to see the best up-to-date 4Story content for Spain and also check out these interesting facts you probably never knew about 4story.es
Visit 4story.esWe analyzed 4story.es page load time and found that the first response time was 471 ms and then it took 71.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
4story.es performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value16.8 s
0/100
25%
Value10.2 s
8/100
10%
Value2,460 ms
5/100
30%
Value0.247
50/100
15%
Value22.0 s
1/100
10%
471 ms
717 ms
313 ms
356 ms
716 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 4story.es, 26% (22 requests) were made to Gf1.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 (5.9 sec) relates to the external source Static.doubleclick.net.
Page size can be reduced by 1.3 MB (27%)
4.8 MB
3.5 MB
In fact, the total size of 4story.es main page is 4.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 108.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. This page needs HTML code to be minified as it can gain 25.0 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 108.4 kB or 83% of the original size.
Potential reduce by 3.4 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 644.9 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 644.9 kB or 65% of the original size.
Potential reduce by 522.9 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.es needs all CSS files to be minified and compressed as it can save up to 522.9 kB or 82% of the original size.
Number of requests can be reduced by 33 (41%)
81
48
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 29 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
4story.es
471 ms
es.4story.gameforge.com
717 ms
f6763cdbc2ed563e6dabdfbcd9e53a.css
313 ms
38ef77dbb86fe1861565522048757b.css
356 ms
30325903cf4267fd4ee6887940f667.css
716 ms
eeaead4680de9f26323b889fe76e4e.css
633 ms
94e9c988775d4d9602df27aaa69c04.css
272 ms
d55973f091809f12086605c680624f.js
705 ms
32296d48ee3740c4f071969d20d006.js
1722 ms
74a2472b07741e6900b40d529efc36.js
280 ms
a7e7115215785502490da6c890ee95.js
239 ms
94da4a34cdb09b074ea89e4396df7e.js
1720 ms
20407a47f5b7d7c3f695cf2ca6327b.js
594 ms
522294ce028fa74553bf223473e13c.js
661 ms
d125e4b15d947ef5084affffc7b85d.js
289 ms
356416b592bd7ee5c8539905d40ce7.js
575 ms
8d3acd9fa6dbc3b1d17f16c7936aac.js
647 ms
f33f613c053ffb5dba80074dc1d59e.js
191 ms
b11ba3a629b2afb593b71eee16c9cf.js
1506 ms
b3ba493bd716fd33b9ff54223c7895.js
247 ms
7116a2b08d6e90406f63724abd7b44.js
248 ms
c7a759afa23c3ae3bae667b596e9d1.js
253 ms
c290a391c0d68ef105015f0a0bb098.js
1469 ms
aff63c906844802235d91cbe406e06.js
1617 ms
2afbea55e85fae57c4ed5977918cf6.js
1440 ms
eccf4b6441b7bbdd817a1dd9ba808f.js
188 ms
functions.js
1588 ms
59ad78df222be12ef3c12bf518a47d.jpg
2537 ms
97342be639b3ad38305dbb0181a40b.png
350 ms
ebf2dabe3cd1d8e0c225c8b8ecb085.png
484 ms
d61df2a01926955510b875f6b1be9d.jpg
483 ms
f410a3e2c90af68bdec24c0fa732aa.png
1195 ms
8e16e2d10a9a74f6420767ecd68c0e.jpg
1191 ms
a1bf3e2ba87b3b6193ce7e0bc44903.png
1019 ms
15d414403178270294ffb516e06e25.jpg
1275 ms
61e2f779bf1e832e24df079a927e99.png
1143 ms
3ae9063a7415d0ee62703129786fa5.png
1389 ms
0aadc758a4498e33a8d89b0b0dde00.png
1119 ms
7dfe2628b2a2370fe0243be9bcc93d.jpg
1175 ms
8ec364e829a3c7324546e3a8d83478.jpg
1141 ms
6c7951ba22709e2ab87a627cf7fd65.jpg
1363 ms
99cfaa6b52934834f249cd64d5bec9.png
1314 ms
c0edcb00625bf9bf274d5000d798db.png
1353 ms
a0bde00d3bbda5afe791d07628468c.jpg
1305 ms
b171da6dc2373324a8162ffc71c232.png
1306 ms
0ff6448f058ac3a63509016f3d63f6.png
1306 ms
e33da11dfe7f3e0c511125dbdd95ee.png
1354 ms
e0d5cf79041f8f6107d2ba197374ff.gif
1353 ms
5a96a565163170ba492430fa1e11ef.png
1352 ms
fc9424f9f0e5f60d1e5e3f5b6e30c1.jpg
1305 ms
4771502d9ac7e7cb594aea4a41371a.jpg
1304 ms
23c707acfb5532ed7608bbee4f24fb.png
1306 ms
6a7805684d88cddd0e5e5f395e5572.png
1304 ms
4f4b3a18939fe179d7792e145ea15c.jpg
1353 ms
KzroQJRM1tg
665 ms
ajs.php
780 ms
www-player-vflMqr8uC.css
1326 ms
www-embed-player.js
346 ms
base.js
2267 ms
a192d3f34423ed43b9e072f3136e79.png
1438 ms
64d3e0be4f9ad51ec0c8e66ad2cf65.jpg
1436 ms
7e107d96490a49c772978f70910e3e.jpg
1225 ms
lg.php
1489 ms
de3d5a926f41bd1838ca3d7f2df673.jpg
1225 ms
E6gg7P33.js
4422 ms
ga.js
52 ms
__utm.gif
678 ms
id
3382 ms
YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js
3714 ms
ad_status.js
5899 ms
atrk.js
5841 ms
2d40928b486ee1ece704628d8c9e20.bg
2784 ms
GT7h68ox.js
1203 ms
logo_ringo-vflOpz8ZI.png
1112 ms
24c9a6c60ffe7e0a60cc6ed55bdf6f.sprites
870 ms
71fe874d78b03e38e06a3b471f6224.png
386 ms
al.php
0 ms
75c446aafdfbf67356490c997806e3.png
5489 ms
6cbace8ebf36bce41afd56ad0fbe49.png
5492 ms
645baafaf1abbc2a81a769401ec354.jpg
3808 ms
lg.php
632 ms
cb3528756ea8294af635442c714b16.jpg
629 ms
2de8406e53691afa7fb7218384ba97.jpg
620 ms
aa160d77c0fafe4b0995445bef1c42.jpg
615 ms
atrk.gif
1021 ms
test.png
422 ms
4story.es 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.es 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
4story.es 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
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4story.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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.es 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.es
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: