3.6 sec in total
721 ms
2.6 sec
328 ms
Visit aquastatus.ru now to see the best up-to-date Aquastatus content for Russia and also check out these interesting facts you probably never knew about aquastatus.ru
Форум аквариумистов. Аквариумный форум AQUASTATUS.RU. Aquarium forum for all aquarists
Visit aquastatus.ruWe analyzed Aquastatus.ru page load time and found that the first response time was 721 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
aquastatus.ru performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value17.7 s
0/100
25%
Value13.5 s
2/100
10%
Value10,580 ms
0/100
30%
Value0.67
8/100
15%
Value26.0 s
0/100
10%
721 ms
125 ms
235 ms
236 ms
241 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 48% of them (27 requests) were addressed to the original Aquastatus.ru, 23% (13 requests) were made to Vk.com and 7% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (721 ms) belongs to the original domain Aquastatus.ru.
Page size can be reduced by 448.0 kB (64%)
700.8 kB
252.8 kB
In fact, the total size of Aquastatus.ru main page is 700.8 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. 35% of websites need less resources to load. Javascripts take 486.5 kB which makes up the majority of the site volume.
Potential reduce by 27.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 27.8 kB or 75% 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. Obviously, Aquastatus needs image optimization as it can save up to 10.2 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 345.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 345.1 kB or 71% of the original size.
Potential reduce by 65.0 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. Aquastatus.ru needs all CSS files to be minified and compressed as it can save up to 65.0 kB or 71% of the original size.
Number of requests can be reduced by 21 (40%)
53
32
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aquastatus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
aquastatus.ru
721 ms
wp-emoji-release.min.js
125 ms
styles.css
235 ms
default-style.css
236 ms
nav-style.css
241 ms
css
25 ms
genericons.css
245 ms
style.css
310 ms
responsive.css
307 ms
jquery.js
586 ms
jquery-migrate.min.js
360 ms
openapi.js
386 ms
jquery.form.min.js
359 ms
scripts.js
365 ms
1_0_5179AEFF_5179AEFF_1_uniques
358 ms
honeycomb.png
123 ms
up_nofocus.png
120 ms
down_nofocus.png
162 ms
logo.png
118 ms
%D1%82%D0%B5%D1%82%D1%80%D0%B0%D1%85%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8%D0%BE%D0%B7-150x100.jpg
121 ms
%D0%92%D0%BE%D0%B4%D0%B0-%D0%B2-%D0%B0%D0%BA%D0%B2%D0%B0%D1%80%D0%B8%D1%83%D0%BC%D0%B5-133x100.jpg
176 ms
%D0%A1%D0%B8%D0%BD%D0%B5-%D0%B7%D0%B5%D0%BB%D0%B5%D0%BD%D1%8B%D0%B5-%D0%B2%D0%BE%D0%B4%D0%BE%D1%80%D0%BE%D1%81%D0%BB%D0%B8_-150x98.jpg
243 ms
%D0%94%D0%B8%D0%B0%D1%82%D0%BE%D0%BC%D0%BE%D0%B2%D1%8B%D0%B5-%D0%B2%D0%BE%D0%B4%D0%BE%D1%80%D0%BE%D1%81%D0%BB%D0%B8-133x100.jpg
256 ms
%D0%A7%D0%B5%D1%80%D0%BD%D0%B0%D1%8F-%D0%B1%D0%BE%D1%80%D0%BE%D0%B4%D0%B0-150x100.jpg
252 ms
%D0%9D%D0%B8%D1%82%D1%87%D0%B0%D1%82%D0%BA%D0%B0-%D0%B2-%D0%B0%D0%BA%D0%B2%D0%B0%D1%80%D0%B8%D1%83%D0%BC%D0%B5-121x100.jpg
254 ms
%D0%A6%D0%B2%D0%B5%D1%82%D0%B5%D0%BD%D0%B8%D0%B5-%D0%B2%D0%BE%D0%B4%D1%8B-%D0%B2-%D0%B0%D0%BA%D0%B2%D0%B0%D1%80%D0%B8%D1%83%D0%BC%D0%B5-150x82.jpg
315 ms
%D0%9D%D0%B5%D0%BB%D1%8C%D0%B7%D1%8F-%D0%B2%D0%B5%D1%80%D0%B8%D1%82%D1%8C-%D0%BF%D1%80%D0%BE%D0%B4%D0%B0%D0%B2%D1%86%D0%B0%D0%BC-%D0%B0%D0%BA%D0%B2%D0%B0%D1%80%D0%B8%D1%83%D0%BC%D0%BD%D1%8B%D1%85-%D0%B7%D0%BE%D0%BE%D0%BC%D0%B0%D0%B3%D0%B0%D0%B7%D0%B8%D0%BD%D0%BE%D0%B2-150x90.jpg
330 ms
%D0%9C%D1%83%D1%82%D0%BD%D0%B0%D1%8F-%D0%B2%D0%BE%D0%B4%D0%B0-%D0%B2-%D0%B0%D0%BA%D0%B2%D0%B0%D1%80%D0%B8%D1%83%D0%BC%D0%B5-150x84.jpg
359 ms
%D0%A1%D0%BE%D0%B2%D0%BC%D0%B5%D1%81%D1%82%D0%B8%D0%BC%D0%BE%D1%81%D1%82%D1%8C-%D0%B0%D0%BA%D0%B2%D0%B0%D1%80%D0%B8%D1%83%D0%BC%D0%BD%D1%8B%D1%85-%D1%80%D1%8B%D0%B1-133x100.jpg
370 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
37 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
37 ms
upload.gif
129 ms
watch.js
500 ms
widget_community.php
308 ms
piwik.js
475 ms
loader_nav19127_3.js
129 ms
lite.css
131 ms
lite.js
513 ms
lang3_0.js
257 ms
widget_community.css
258 ms
xdm.js
259 ms
al_community.js
262 ms
advert.gif
85 ms
1
84 ms
TW0HgrvsDUQ.jpg
394 ms
-pzZvMUOifI.jpg
380 ms
C44XVup4Pug.jpg
395 ms
QE1WnJcbUUw.jpg
380 ms
e_6624aaad.jpg
391 ms
eQg43M9yU24.jpg
388 ms
-28tJqu_6Ok.jpg
398 ms
IDZqsSYnWtk.jpg
395 ms
IbMPX679cuY.jpg
398 ms
camera_50.png
129 ms
deactivated_50.png
130 ms
w_logo.png
132 ms
aquastatus.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
aquastatus.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
aquastatus.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aquastatus.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 Aquastatus.ru 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.
aquastatus.ru
Open Graph description is not detected on the main page of Aquastatus. 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: