983 ms in total
68 ms
651 ms
264 ms
Visit westeros.org now to see the best up-to-date Westeros content for United States and also check out these interesting facts you probably never knew about westeros.org
Westeros is the premiere fansite for George R.R. Martin's epic fantasy series 'A Song of Ice and Fire' and the HBO-show 'Game of Thrones'.
Visit westeros.orgWe analyzed Westeros.org page load time and found that the first response time was 68 ms and then it took 915 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
westeros.org performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value5.1 s
24/100
25%
Value2.5 s
98/100
10%
Value320 ms
76/100
30%
Value0.291
41/100
15%
Value5.8 s
67/100
10%
68 ms
204 ms
96 ms
143 ms
51 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 46% of them (17 requests) were addressed to the original Westeros.org, 30% (11 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (204 ms) belongs to the original domain Westeros.org.
Page size can be reduced by 29.1 kB (6%)
496.5 kB
467.4 kB
In fact, the total size of Westeros.org main page is 496.5 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. 45% of websites need less resources to load. Images take 423.7 kB which makes up the majority of the site volume.
Potential reduce by 27.0 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 27.0 kB or 71% of the original size.
Potential reduce by 334 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. Westeros images are well optimized though.
Potential reduce by 1.8 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.
Number of requests can be reduced by 7 (29%)
24
17
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Westeros. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
westeros.org
68 ms
westeros.org
204 ms
www.westeros.org
96 ms
www.westeros.org
143 ms
css
51 ms
js
69 ms
addthis_widget.js
38 ms
jquery.min.js
37 ms
snippet.js
65 ms
lite-youtube.js
36 ms
sdk.js
31 ms
bg_parchment.png
55 ms
bg_parchment-light.png
88 ms
bg_border.png
86 ms
header_left-shield-westeros.png
54 ms
header_right-shield-westeros.png
86 ms
bg_enamel-gold.png
85 ms
bg_enamel-got.png
109 ms
icon_index-asoiaf.png
91 ms
icon_index-awoiaf.png
109 ms
icon_index-westeros.png
108 ms
icon_index-citadel.png
87 ms
icon_index-bod.png
109 ms
5aUz9_-1phKLFgshYDvh6Vwt7VptuA.ttf
45 ms
5aUu9_-1phKLFgshYDvh6Vwt5eFIqEp2jg.ttf
49 ms
sdk.js
9 ms
main.js
26 ms
50 ms
4UacrEBBsBhlBjvfkQjt71kZfyBzPgNG9hU4-6qm.ttf
5 ms
4UacrEBBsBhlBjvfkQjt71kZfyBzPgNGERI4-6qm.ttf
20 ms
N0bM2S5WOex4OUbESzoESK-i-MfWQZE.ttf
78 ms
taiOGmRtCJ62-O0HhNEa-Z6v2ZU.ttf
33 ms
taiTGmRtCJ62-O0HhNEa-ZYU_IU2SK8.ttf
33 ms
4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlbgv5qhmSA.ttf
34 ms
4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlYHuJqhmSA.ttf
53 ms
5aUt9_-1phKLFgshYDvh6Vwt7V9dv21W.ttf
32 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VBEhGiU9D.ttf
33 ms
westeros.org accessibility score
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
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
Form elements do not have associated labels
Links do not have a discernible name
westeros.org 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
Browser errors were logged to the console
Page has valid source maps
westeros.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Westeros.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Westeros.org 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.
westeros.org
Open Graph description is not detected on the main page of Westeros. 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: