7 sec in total
1.3 sec
5.1 sec
617 ms
Welcome to szona.org homepage info - get ready to check Szona best content for Russia right away, or after learning these important things about szona.org
Актуальная и интересная информация о инновациях в бизнес среде
Visit szona.orgWe analyzed Szona.org page load time and found that the first response time was 1.3 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
szona.org performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value8.6 s
1/100
25%
Value15.9 s
0/100
10%
Value2,530 ms
4/100
30%
Value0
100/100
15%
Value37.7 s
0/100
10%
1282 ms
532 ms
135 ms
386 ms
494 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 37% of them (39 requests) were addressed to the original Szona.org, 46% (48 requests) were made to St6-21.vk.com and 6% (6 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source St6-21.vk.com.
Page size can be reduced by 551.8 kB (7%)
8.0 MB
7.4 MB
In fact, the total size of Szona.org main page is 8.0 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. 65% of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 27.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. 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.5 kB or 74% of the original size.
Potential reduce by 77.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. Szona images are well optimized though.
Potential reduce by 309.4 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 309.4 kB or 15% of the original size.
Potential reduce by 137.1 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. Szona.org needs all CSS files to be minified and compressed as it can save up to 137.1 kB or 23% of the original size.
Number of requests can be reduced by 61 (59%)
103
42
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Szona. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
szona.org
1282 ms
szona.org
532 ms
index.php
135 ms
index.php
386 ms
index.php
494 ms
style.css
623 ms
navcontrol.js
374 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
229 ms
aci.js
659 ms
1694636845_oblozhka-k-state.jpg
240 ms
1699040780_565444576.jpeg
374 ms
1699392596_756766e5678.jpg
371 ms
1705443944_83000.png
1084 ms
1703774813_2333008.jpeg
358 ms
1709209461_656545678.jpg
475 ms
1711278429_1-.jpg
511 ms
1708047468_1675963049_5197-.jpg
477 ms
1678119771_1.jpeg
741 ms
1678032960_1.jpeg
500 ms
1677854453_1.jpeg
717 ms
1677601611_1.jpg
596 ms
1677433064_3.jpg
628 ms
1677322553_1.jpeg
764 ms
1677172581_1.jpeg
837 ms
1676909011_1.jpeg
1083 ms
1676817170_1.jpeg
955 ms
1676563900_1.jpeg
867 ms
1676391968_2.jpeg
1084 ms
1676223590_2.jpg
957 ms
1676115423_3.jpg
995 ms
1675873803_2.jpg
1084 ms
1675787178_2.jpg
1084 ms
1675507888_1.jpeg
1119 ms
1675356162_1.jpeg
1128 ms
1670344425_1.jpeg
1131 ms
tag.js
1000 ms
bg-header.png
1106 ms
100.png
1151 ms
menu-line.png
1154 ms
navigation.jpg
1201 ms
bg-footer1.png
1174 ms
upload.gif
115 ms
hit
671 ms
widget_community.php
280 ms
bg-menu-link.png
1152 ms
loader_nav211214281431_3.js
286 ms
fonts_cnt.c7a76efe.css
941 ms
lite.c9bfd4eb.css
731 ms
lang3_2.js
566 ms
polyfills.c3a1b892.js
711 ms
vkui.278a6bf3.css
782 ms
xdm.js
624 ms
ui_common.f1e97277.css
710 ms
vkcom-kit.9f1749da.css
885 ms
vkcom-kit.5279814c.js
1051 ms
react.6a15a5cc.js
912 ms
vkcom-kit-icons.a43a129b.js
919 ms
vkui.5a4aa7ce.js
1046 ms
state-management.a46c500d.js
1008 ms
architecture-mobx.0151929f.js
1010 ms
audioplayer-lib.93b52d88.css
1007 ms
audioplayer-lib.09891d25.js
1040 ms
bootstrap.d7a015b7.js
1295 ms
core_spa.ba907845.js
1094 ms
common.fbb82d86.js
1307 ms
7f463667.b3f6bf8c.js
1123 ms
ui_common.43d06ff5.css
1127 ms
ui_common.09223a36.js
1136 ms
audioplayer.43d06ff5.css
1171 ms
audioplayer.c847163d.js
1200 ms
widget_community.4978d481.css
1209 ms
6056d482.aa111ad0.js
1220 ms
5233f55c.4d962db2.js
1252 ms
23cad2f0.edafaf00.js
1280 ms
82fab9f9.32f2ca13.js
1293 ms
likes.43d06ff5.css
1300 ms
likes.642b107f.js
1333 ms
vkcom-kit.4833a6b6.css
1364 ms
vkcom-kit.1b25768e.js
1393 ms
vkcom-kit-icons.b98046f5.js
1384 ms
architecture-mobx.d853b516.js
1390 ms
audioplayer-lib.85b39ca5.css
1387 ms
audioplayer-lib.a6e6e8bc.js
1439 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
324 ms
community.640eed5d.css
822 ms
base.763c8de4.css
769 ms
react.84cfd9aa.js
776 ms
advert.gif
684 ms
state-management.60b70a9c.js
742 ms
vkui.3fd7d465.js
746 ms
c3d11fba.f6060966.js
645 ms
0fc69f32.22f2cf1d.js
618 ms
79661701.993e9d31.js
653 ms
57703e15.d612be1a.js
566 ms
edb6ffde.ec4932a7.js
623 ms
community.48c79df5.js
602 ms
sync_cookie_image_decide
136 ms
cgQFwzpczqrFK_BM4fNeWKiB0N1UyMqpa7QbjcNZzHN_u7LzzcKv8i4bpLfqC8bD-uE2V5rq.jpg
468 ms
QulWsGFAn5k.png
612 ms
6-eD9H4bl2fkEHlUUvZ_J7u34-aKhieDkNnMyP1KKElon37SM9JCgwxa-xLI3Qq6ijSJrKo06NU_FJy1J-sDcXbM.jpg
360 ms
K9KEDC1r_mPnpMTB2OgbXDm9LtxoUjGCuil4V_jmSoVzSEpmtRhTuLCfwfHZ938Ij8UX45O7.jpg
450 ms
-Q6-2DyuG9GsI8rfV-Y5DDN3XEiM_rMFLyK91P-oJXK8aEXNPX_MsKXjtbnWoADELdNvYqLSyYW4jwmQ4VF95G0d.jpg
475 ms
2ipFS-1KuvygHy_GXjfKDczu9Er4GqccH-3LKXXfeUCiB1cFn1Angb99cJIfEis-V0xGBdxtZEExq6E93uTcL8mS.jpg
476 ms
upload.gif
82 ms
1
146 ms
szona.org accessibility score
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
Links do not have a discernible name
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
szona.org 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
szona.org SEO score
![]()
RU
![]()
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Szona.org can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Szona.org 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.
szona.org
Open Graph description is not detected on the main page of Szona. 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: