7.2 sec in total
451 ms
6.3 sec
428 ms
Visit doomquake.ru now to see the best up-to-date Doomquake content for Russia and also check out these interesting facts you probably never knew about doomquake.ru
Doom и Quake фан сайт, скачать игру и патчи, коды и читы, картинки и обои, мы любим эти игры!
Visit doomquake.ruWe analyzed Doomquake.ru page load time and found that the first response time was 451 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
doomquake.ru performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
451 ms
110 ms
217 ms
231 ms
234 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 32% of them (46 requests) were addressed to the original Doomquake.ru, 8% (11 requests) were made to Cstatic.weborama.fr and 7% (10 requests) were made to Rtb.am15.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Bnhtml.com.
Page size can be reduced by 128.0 kB (25%)
514.0 kB
386.0 kB
In fact, the total size of Doomquake.ru main page is 514.0 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. 30% of websites need less resources to load. Images take 384.5 kB which makes up the majority of the site volume.
Potential reduce by 27.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. 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.2 kB or 76% of the original size.
Potential reduce by 45.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. Obviously, Doomquake needs image optimization as it can save up to 45.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 42.1 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 42.1 kB or 54% of the original size.
Potential reduce by 12.8 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. Doomquake.ru needs all CSS files to be minified and compressed as it can save up to 12.8 kB or 80% of the original size.
Number of requests can be reduced by 59 (47%)
125
66
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doomquake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
doomquake.ru
451 ms
style.css
110 ms
engine.css
217 ms
menu.js
231 ms
dle_ajax.js
234 ms
js_edit.js
237 ms
highslide.js
239 ms
loading.gif
110 ms
1269255251_sh0.jpg
217 ms
1274977966_sh0.jpg
113 ms
1269005154_11.jpg
115 ms
1269005181_12.jpg
120 ms
1269005214_13.jpg
117 ms
1269005224_10.jpg
217 ms
1269001616_1.jpg
220 ms
1269001562_2.jpg
227 ms
1269001598_3.jpg
228 ms
1269000142_2677.jpg
230 ms
1268997950_2676.jpg
322 ms
1268986682_2675.jpg
323 ms
1268920374_2.jpg
330 ms
1268920391_3.jpg
338 ms
1268920415_4.jpg
337 ms
1268922696_2674.jpg
342 ms
1268922687_2673.jpg
428 ms
singlepixel.gif
429 ms
1269197993_sh0.jpg
436 ms
1269198390_sh0.jpg
447 ms
1269251823_sh0.jpg
448 ms
1269252163_sh0.jpg
452 ms
1269253096_sh0.jpg
533 ms
bg-trans-dropmenu.png
532 ms
logosite.jpg
646 ms
crossline.png
520 ms
bg-bg-left.gif
534 ms
bg-bg-right.gif
538 ms
bg-title.png
542 ms
bg-menu.png
617 ms
bg-data.gif
619 ms
spacer.gif
628 ms
bg-title-right.png
645 ms
header_search_background.png
649 ms
header_search_select_button.png
654 ms
hit
264 ms
r3.html
704 ms
r2.html
654 ms
r1.html
659 ms
bottom-line.png
673 ms
hit
133 ms
games1.html
381 ms
games2.html
387 ms
games3.html
382 ms
ams2.html
542 ms
a1.html
530 ms
a4.html
534 ms
advert.js
200 ms
bn.php
405 ms
advert.js
157 ms
bn.php
405 ms
zrxNDQ5Njc5NjU1
78 ms
banner
137 ms
185_20442-160x600.png
206 ms
tizer_view.js
34 ms
adv_from_ca.gif
264 ms
uid.php
134 ms
fpx.php
419 ms
405 ms
uid.php
133 ms
fpx.php
416 ms
416 ms
dsp
544 ms
advmaker
429 ms
rsc.php
478 ms
advmaker
194 ms
rsc.php
381 ms
dsp
527 ms
advmaker
98 ms
renegade-smart
196 ms
pixel
17 ms
emily
267 ms
audtd.png
637 ms
sync
338 ms
sync
425 ms
556d807310823b694772f699.js
218 ms
pixel
14 ms
bn1.php
398 ms
ambn.png
325 ms
sync
247 ms
advmaker-sync
490 ms
sync
284 ms
bn1.php
410 ms
renegade-smart
99 ms
sync
631 ms
sync
141 ms
sync
623 ms
sync
617 ms
sync
131 ms
dispatch.fcgi
173 ms
dispatch.fcgi
178 ms
pixel
35 ms
pixel.gif
95 ms
sync
779 ms
admitad
244 ms
sync
718 ms
bn2.php
206 ms
bn2.php
205 ms
external_all.html
63 ms
sync
352 ms
sync
328 ms
external_libs.js
31 ms
external_tracking.fcgi
173 ms
dispatch.fcgi
181 ms
dispatch.fcgi
197 ms
pixel.gif
20 ms
5576c7bab8b6b.html
290 ms
ac9d0db86a53e3ef661eafc7d848c140.png
205 ms
13071801.js
35 ms
transp.gif
60 ms
transp.gif
57 ms
transp.gif
51 ms
transp.gif
51 ms
weborama.js
179 ms
sync
211 ms
transp.gif
37 ms
invoke.js
1282 ms
401736.gif
8 ms
get
396 ms
hdmr.sddan.com
321 ms
graphinium_match.php
486 ms
pixel.gif
168 ms
dn_iframe.js
467 ms
transp.gif
31 ms
transp.gif
29 ms
sync
283 ms
sync
267 ms
transp.gif
29 ms
dn.html
155 ms
dn.js
161 ms
get_delivery_data.php
241 ms
rteasdt.html
485 ms
script_graphinium.php
162 ms
watch
288 ms
retrieve.js
158 ms
doomquake.ru 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
doomquake.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
doomquake.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doomquake.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Doomquake.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.
doomquake.ru
Open Graph description is not detected on the main page of Doomquake. 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: