7.2 sec in total
1.6 sec
5 sec
553 ms
Click here to check amazing Sword And Sorcery content. Otherwise, check out these important facts you probably never knew about sword-and-sorcery.com
Visit sword-and-sorcery.comWe analyzed Sword-and-sorcery.com page load time and found that the first response time was 1.6 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sword-and-sorcery.com performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value23.8 s
0/100
25%
Value26.6 s
0/100
10%
Value3,200 ms
2/100
30%
Value0.411
24/100
15%
Value30.6 s
0/100
10%
1613 ms
537 ms
120 ms
353 ms
245 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 43% of them (40 requests) were addressed to the original Sword-and-sorcery.com, 39% (36 requests) were made to Fonts.gstatic.com and 9% (8 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Sword-and-sorcery.com.
Page size can be reduced by 1.1 MB (28%)
3.9 MB
2.8 MB
In fact, the total size of Sword-and-sorcery.com main page is 3.9 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. 85% 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 257.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 257.3 kB or 86% of the original size.
Potential reduce by 10.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. Sword And Sorcery images are well optimized though.
Potential reduce by 740.6 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 740.6 kB or 63% of the original size.
Potential reduce by 72.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. Sword-and-sorcery.com needs all CSS files to be minified and compressed as it can save up to 72.2 kB or 49% of the original size.
Number of requests can be reduced by 26 (51%)
51
25
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sword And Sorcery. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.sword-and-sorcery.com
1613 ms
rs6.css
537 ms
front.min.css
120 ms
jquery.min.js
353 ms
jquery-migrate.min.js
245 ms
revolution.tools.min.js
732 ms
rs6.min.js
971 ms
et-core-unified-52854.min.css
326 ms
css
34 ms
mediaelementplayer-legacy.min.css
321 ms
wp-mediaelement.min.css
366 ms
scripts.min.js
1020 ms
smoothscroll.js
445 ms
jquery.fitvids.js
456 ms
easypiechart.js
483 ms
salvattore.js
613 ms
front.min.js
596 ms
common.js
595 ms
mediaelement-and-player.min.js
1018 ms
mediaelement-migrate.min.js
703 ms
wp-mediaelement.min.js
727 ms
wood_bg_black.png
860 ms
logo@2.png
608 ms
transparent.png
120 ms
ancient_chroicles_bg.jpg
608 ms
enemie_right.png
571 ms
heroes.png
572 ms
ememies_left.png
605 ms
SS_logo_big.png
779 ms
divider.png
1036 ms
New_SS_Website_800x500_2-400x250.jpg
607 ms
Fan_made_quests_800x500-400x250.jpg
607 ms
Q_A_800x500-400x250.jpg
788 ms
logo-gremlins@2.png
860 ms
logo-ares@2.png
789 ms
FB_icon2020.svg
986 ms
YT_icon2020.svg
988 ms
JfVXVKZ7o_A
135 ms
video_screen.jpg
955 ms
et-divi-dynamic-tb-52265-52854-late.css
726 ms
S6uyw4BMUTPHjxAwWA.woff
28 ms
S6uyw4BMUTPHjxAwWw.ttf
32 ms
S6u9w4BMUTPHh7USSwaPHw.woff
32 ms
S6u9w4BMUTPHh7USSwaPHA.ttf
32 ms
S6u8w4BMUTPHh30AUi-s.woff
33 ms
S6u8w4BMUTPHh30AUi-v.ttf
32 ms
S6u9w4BMUTPHh6UVSwaPHw.woff
36 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
37 ms
S6u9w4BMUTPHh50XSwaPHw.woff
39 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
38 ms
S6u8w4BMUTPHjxsAUi-s.woff
38 ms
S6u8w4BMUTPHjxsAUi-v.ttf
39 ms
S6u_w4BMUTPHjxsI9w2_FQfr.woff
38 ms
S6u_w4BMUTPHjxsI9w2_FQfo.ttf
39 ms
S6u-w4BMUTPHjxsIPx-mPCQ.woff
43 ms
S6u-w4BMUTPHjxsIPx-mPCc.ttf
44 ms
S6u_w4BMUTPHjxsI5wq_FQfr.woff
44 ms
S6u_w4BMUTPHjxsI5wq_FQfo.ttf
45 ms
S6u_w4BMUTPHjxsI3wi_FQfr.woff
44 ms
S6u_w4BMUTPHjxsI3wi_FQfo.ttf
45 ms
modules.woff
805 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-uTnfYPlCw.woff
63 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-uTnfYPlCA.ttf
66 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfYPlCw.woff
46 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfYPlCA.ttf
70 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-gjgfYPlCw.woff
45 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-gjgfYPlCA.ttf
66 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-jHgfYPlCw.woff
46 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-jHgfYPlCA.ttf
74 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-lbgfYPlCw.woff
70 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-lbgfYPlCA.ttf
89 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-n_gfYPlCw.woff
94 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-n_gfYPlCA.ttf
511 ms
www-player.css
10 ms
www-embed-player.js
29 ms
base.js
57 ms
ad_status.js
240 ms
wAFWjcG1j0S59k6y9gmRkscrkcYt8sjUn-04af-yL2Q.js
174 ms
embed.js
76 ms
KFOmCnqEu92Fr1Mu4mxM.woff
18 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
18 ms
id
29 ms
Create
189 ms
GenerateIT
53 ms
loader.gif
187 ms
qoe
11 ms
log_event
1 ms
JfVXVKZ7o_A
227 ms
KFOmCnqEu92Fr1Mu4mxM.woff
25 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
23 ms
ad_status.js
77 ms
id
42 ms
sword-and-sorcery.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
sword-and-sorcery.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
sword-and-sorcery.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
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
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 Sword-and-sorcery.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 Sword-and-sorcery.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.
sword-and-sorcery.com
Open Graph description is not detected on the main page of Sword And Sorcery. 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: