3.2 sec in total
163 ms
2.5 sec
562 ms
Click here to check amazing Capital content for United States. Otherwise, check out these important facts you probably never knew about capital.ua
Деловой портал «Капитал»
Visit capital.uaWe analyzed Capital.ua page load time and found that the first response time was 163 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
capital.ua performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value11.2 s
0/100
25%
Value12.4 s
3/100
10%
Value1,340 ms
17/100
30%
Value0.705
7/100
15%
Value18.0 s
3/100
10%
163 ms
184 ms
323 ms
112 ms
34 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 36% of them (38 requests) were addressed to the original Capital.ua, 9% (10 requests) were made to Static.xx.fbcdn.net and 8% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (871 ms) relates to the external source Content.adriver.ru.
Page size can be reduced by 589.9 kB (27%)
2.2 MB
1.6 MB
In fact, the total size of Capital.ua main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 101.4 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 14.7 kB, which is 12% 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 101.4 kB or 81% of the original size.
Potential reduce by 20.5 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. Capital images are well optimized though.
Potential reduce by 460.0 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 460.0 kB or 35% of the original size.
Potential reduce by 8.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. Capital.ua needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 20% of the original size.
Number of requests can be reduced by 58 (57%)
101
43
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capital. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
capital.ua
163 ms
www.capital.ua
184 ms
client.js
323 ms
ti.js
112 ms
optimized.css
34 ms
optimized.js
61 ms
adriver.core.2.js
50 ms
highstock.js
57 ms
highstock_options.js
138 ms
exporting.js
52 ms
charts.js
51 ms
gpt.js
133 ms
1-2
217 ms
platform.js
105 ms
email-decode.min.js
106 ms
conversion.js
120 ms
autoUpdate.adriver.js
871 ms
analytics.js
178 ms
fbds.js
180 ms
sdk.js
182 ms
pattern.jpg
48 ms
apps_tabs.png
49 ms
logo.png
176 ms
a3b4079ead7dff92b330a7aacedcea2fd3c107c5.jpg
176 ms
6dbaa5476eadfecbd243a9d9725f2aa846ac46c3.jpg
174 ms
fcb3ee0fa8619c142c53158e6dd992c7221bf9a8.jpg
177 ms
ad2b289220f47a7771f592c509f89170ec444c55.jpg
179 ms
4ef09a8856ed8748012b4c7f4684ab2bf22a2b76.jpg
180 ms
a0cd818230ddd3a09c78e5188cc1e9fc9bb7181e.jpg
180 ms
72d583b71895bb50a8c6c18dd979d64afcfb8c13.jpg
179 ms
db9e8494b099ca84ba8d1a41d9bed4d28cdf1d1f.jpg
177 ms
6e5dfaea80e69af868b5eccc122bde1537a9ae91.jpg
204 ms
f9c7c112497104e7e82945f316ecd24a79da0f46.jpg
203 ms
ddd727730d4f1c9b70e199941d1e900765139e3e.jpg
204 ms
capital_small.png
203 ms
adv_ico.gif
202 ms
pubads_impl.js
195 ms
header_shadow.png
161 ms
src_ico.gif
161 ms
ico.png
161 ms
capital_subscribe.png
162 ms
line_sep.gif
160 ms
widgets.js
426 ms
384 ms
cb=gapi.loaded_0
47 ms
cb=gapi.loaded_1
234 ms
subscribe_embed
312 ms
newspaper.png
231 ms
line_sep_v.gif
227 ms
light_bg.png
227 ms
bg_direction_nav.png
227 ms
MoreWebPro-Bold.woff
283 ms
collect
203 ms
collect
297 ms
sdk.js
202 ms
ads
600 ms
container.html
148 ms
js
182 ms
postmessageRelay
150 ms
print.css
44 ms
www-subscribe-embed_split_v0.css
21 ms
www-subscribe-embed_v0.js
51 ms
207 ms
AIdro_nCeJ_mIOY0z7rxxDCPfume6KybnJIdLaRM0q3txx9m6w=s48-c-k-c0x00ffffff-no-rj
204 ms
subscribe_button_branded_lozenge.png
46 ms
cb=gapi.loaded_0
8 ms
544727282-postmessagerelay.js
122 ms
rpc:shindig_random.js
110 ms
cb=gapi.loaded_0
6 ms
cb=gapi.loaded_2
16 ms
border_3.gif
5 ms
subscribe_embed
38 ms
spacer.gif
6 ms
bubbleSprite_3.png
6 ms
bubbleDropR_3.png
9 ms
bubbleDropB_3.png
10 ms
www-subscribe-embed-card_v0.css
4 ms
www-subscribe-embed-card_v0.js
6 ms
03.png
653 ms
1458358375103808139
101 ms
load_preloaded_resource.js
86 ms
icon.png
49 ms
abg_lite.js
78 ms
window_focus.js
64 ms
qs_click_protection.js
65 ms
b8bba7bdb82ef259240353901c7e809d.js
89 ms
icon.png
21 ms
8603798150558650994
43 ms
iUFT4H_aD2n83E2qiJAm0eQnr0kH-RmNQ6xxrNG4yf8.js
23 ms
sodar
74 ms
page.php
113 ms
sodar2.js
4 ms
runner.html
6 ms
aframe
21 ms
x3qc_J_CTbG.css
78 ms
odEcj4EBDzB.js
89 ms
o1ndYS2og_B.js
80 ms
Ez8TaPyQZ7-.js
84 ms
s23ZuKml3wQ.js
88 ms
_uEhsxKAS3c.js
135 ms
9f_Alkp5qWb.js
85 ms
p55HfXW__mM.js
85 ms
305652375_615602266681136_8921557779273171125_n.png
82 ms
EIDMHaVPVS4.js
31 ms
302719601_615602270014469_1074873769326025746_n.jpg
57 ms
UXtr_j2Fwe-.png
27 ms
capital.ua 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
Links do not have a discernible name
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.
capital.ua 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
capital.ua SEO score
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
Tap targets are not sized appropriately
UK
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capital.ua can be misinterpreted by Google and other search engines. Our service has detected that Ukrainian is used on the page, and it does not match the claimed Russian language. Our system also found out that Capital.ua 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.
capital.ua
Open Graph description is not detected on the main page of Capital. 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: