3.4 sec in total
576 ms
2.7 sec
138 ms
Welcome to draconus.com homepage info - get ready to check Draconus best content right away, or after learning these important things about draconus.com
Independent game development, creators of Hexters and Triplane Turmoil series
Visit draconus.comWe analyzed Draconus.com page load time and found that the first response time was 576 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
draconus.com performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value2.6 s
88/100
25%
Value2.2 s
99/100
10%
Value0 ms
100/100
30%
Value0.005
100/100
15%
Value1.8 s
100/100
10%
576 ms
831 ms
830 ms
833 ms
1200 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 66% of them (19 requests) were addressed to the original Draconus.com, 24% (7 requests) were made to Fonts.gstatic.com and 10% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Draconus.com.
Page size can be reduced by 114.5 kB (24%)
477.3 kB
362.8 kB
In fact, the total size of Draconus.com main page is 477.3 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 325.7 kB which makes up the majority of the site volume.
Potential reduce by 3.9 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 3.9 kB or 68% of the original size.
Potential reduce by 10.2 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. Draconus images are well optimized though.
Potential reduce by 92.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 92.1 kB or 68% of the original size.
Potential reduce by 8.3 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. Draconus.com needs all CSS files to be minified and compressed as it can save up to 8.3 kB or 78% of the original size.
Number of requests can be reduced by 5 (24%)
21
16
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Draconus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for CSS and as a result speed up the page load time.
draconus.com
576 ms
generic.css
831 ms
default.css
830 ms
lightbox.css
833 ms
jquery-1.11.2.min.js
1200 ms
jquery.cycle.all.min.js
954 ms
lightbox.min.js
832 ms
css
24 ms
css
35 ms
css
46 ms
close.png
242 ms
loading.gif
247 ms
prev.png
248 ms
next.png
251 ms
header.png
887 ms
icon_facebook.png
256 ms
icon_twitter.png
483 ms
header_bg.png
579 ms
hr.png
488 ms
capsule_hexters.png
608 ms
capsule_triplane2.png
737 ms
footer.png
732 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
6 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
9 ms
l_rcquZtIOJLfdlcJgi63fesZW2xOQ-xsNqO47m55DA.ttf
13 ms
mbcww3uvDIvQ0VClREeMdJ0EAVxt0G0biEntp43Qt6E.ttf
17 ms
85X_PjV6tftJ0-rX7KYQkJIzTUwDeLjw6S9zIItvw4s.ttf
16 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
16 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
12 ms
draconus.com 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
Links do not have a discernible name
draconus.com 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
draconus.com 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Draconus.com 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 Draconus.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.
draconus.com
Open Graph data is detected on the main page of Draconus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: