3.5 sec in total
792 ms
2.5 sec
204 ms
Click here to check amazing Aurora content. Otherwise, check out these important facts you probably never knew about aurora.ag
Visit aurora.agWe analyzed Aurora.ag page load time and found that the first response time was 792 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
aurora.ag performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value1.5 s
100/100
10%
Value140 ms
95/100
30%
Value0.136
80/100
15%
Value2.9 s
96/100
10%
792 ms
281 ms
125 ms
133 ms
131 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 82% of them (51 requests) were addressed to the original Aurora.ag, 3% (2 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Aurora.ag.
Page size can be reduced by 468.4 kB (40%)
1.2 MB
704.9 kB
In fact, the total size of Aurora.ag main page is 1.2 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. 40% of websites need less resources to load. Images take 591.7 kB which makes up the majority of the site volume.
Potential reduce by 22.5 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. This page needs HTML code to be minified as it can gain 4.6 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.5 kB or 78% of the original size.
Potential reduce by 27.7 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. Aurora images are well optimized though.
Potential reduce by 346.5 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 346.5 kB or 74% of the original size.
Potential reduce by 71.7 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. Aurora.ag needs all CSS files to be minified and compressed as it can save up to 71.7 kB or 87% of the original size.
Number of requests can be reduced by 27 (47%)
57
30
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aurora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
aurora.ag
792 ms
style.css
281 ms
video-js.min.css
125 ms
jquery.bxslider.css
133 ms
jquery.jscrollpane.css
131 ms
css
37 ms
jquery.min.js
143 ms
modernizr.js
136 ms
iscroll.js
747 ms
video.min.js
646 ms
AC_RunActiveContent.js
393 ms
queryLoader.js
395 ms
jquery.fitvids.js
307 ms
jquery.bxslider.min.js
1266 ms
jquery.easing-1.3.pack.js
501 ms
jqueryColor.js
876 ms
jquery.mousewheel.js
765 ms
jquery.jscrollpane.js
991 ms
jquery.metadata.js
878 ms
jquery.validate.js
1101 ms
jquery.hashchange.min.js
1116 ms
jquery.adipoli.min.js
1248 ms
resetdefaultvalue.js
1133 ms
backgroundPosition.js
1060 ms
js
55 ms
TweenMax.min.js
1198 ms
jquery.fittext.js
1185 ms
script.js
1204 ms
loader.gif
146 ms
bg-home.jpg
370 ms
e6d3d0454dd9499bd530f909d4f9fd29_w168_h100_q100.jpg
145 ms
b93a7f35499bdd243ff0f0b1b4f47812_w168_h100_q100.jpg
145 ms
6e79889200f4ea6f8ce0758e62804a17_w168_h100_q100.jpg
152 ms
e37e8b907518db90f0ba73b632912173_w168_h100_q100.jpg
143 ms
eb627e975cbc9616afa727985173b0a2_w168_h100_q100.jpg
165 ms
afa8a30c6d8c691a0de902cf9da589e2_w168_h100_q100.jpg
164 ms
2d9ad763cd21371cb6b12e3d5cf46e1d_w168_h100_q100.jpg
174 ms
be12cb6293260f693de04178eb3433f0_w168_h100_q100.jpg
183 ms
8ebfebb20b2cace6153bf13136ca2489_w168_h100_q100.jpg
219 ms
121b3c661557bbd74c53a463d83bf573_w168_h100_q100.jpg
230 ms
bc4099f844f3ea3568cbec106f0e46ff_w168_h100_q100.jpg
228 ms
8f36061cbbaab90d2af8e76d3a27a02f_w168_h100_q100.jpg
240 ms
04aa54b35de99b53daa443efe69ac879_w168_h100_q100.jpg
252 ms
0131047e5bc237aa6b1367d32dbaeaee_w168_h100_q100.jpg
294 ms
all.js
9 ms
aurora-ag.png
293 ms
aurora-ag-02.png
298 ms
PlayButton.png
307 ms
anMUvcNT0H1YN4FII8wpr93Z6MveExszb-iKWJY7ddA.ttf
11 ms
7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf
11 ms
dosis-regular-webfont.woff
339 ms
dosis-bold-webfont.woff
345 ms
161 ms
plus.png
304 ms
bg-title.png
311 ms
social-networks.png
320 ms
social-networks-2.png
382 ms
xd_arbiter.php
27 ms
xd_arbiter.php
36 ms
like.php
76 ms
qeKvIRsJabD.js
29 ms
LVx-xkvaJ0b.png
21 ms
aurora.ag accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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.
aurora.ag best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
aurora.ag SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aurora.ag 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), while the claimed language is English. Our system also found out that Aurora.ag 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.
aurora.ag
Open Graph description is not detected on the main page of Aurora. 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: