2.9 sec in total
506 ms
2.1 sec
278 ms
Visit fandom.ru now to see the best up-to-date Fandom content for Russia and also check out these interesting facts you probably never knew about fandom.ru
Фэндом: исследование фантастики, клубы любителей фантастики, статьи о фантастике и фантастах. Архив любителей фантастики. Развитие научной фантастики.
Visit fandom.ruWe analyzed Fandom.ru page load time and found that the first response time was 506 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
fandom.ru performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value5.6 s
17/100
25%
Value8.5 s
18/100
10%
Value430 ms
65/100
30%
Value0
100/100
15%
Value11.0 s
21/100
10%
506 ms
627 ms
63 ms
119 ms
262 ms
Our browser made a total of 10 requests to load all elements on the main page. We found that 40% of them (4 requests) were addressed to the original Fandom.ru, 20% (2 requests) were made to Googletagmanager.com and 20% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (669 ms) relates to the external source Acint.net.
Page size can be reduced by 20.8 kB (45%)
46.7 kB
25.9 kB
In fact, the total size of Fandom.ru main page is 46.7 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. Only 5% of websites need less resources to load. HTML takes 29.0 kB which makes up the majority of the site volume.
Potential reduce by 20.8 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 20.8 kB or 72% of the original size.
Potential reduce by 0 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. Fandom images are well optimized though.
Potential reduce by 0 B
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.
We found no issues to fix!
7
7
The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fandom. According to our analytics all requests are already optimized.
fandom.ru
506 ms
www.fandom.ru
627 ms
gtm.js
63 ms
js
119 ms
style.css
262 ms
init
332 ms
top_logo.png
140 ms
aci.js
669 ms
hit
268 ms
hit
539 ms
fandom.ru accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
fandom.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
fandom.ru SEO score
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
![]()
RU
![]()
RU
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fandom.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Fandom.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
fandom.ru
Open Graph description is not detected on the main page of Fandom. 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: