3.8 sec in total
596 ms
2.7 sec
505 ms
Visit epoch.ua now to see the best up-to-date Epoch content for Ukraine and also check out these interesting facts you probably never knew about epoch.ua
Visit epoch.uaWe analyzed Epoch.ua page load time and found that the first response time was 596 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
epoch.ua performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value16.6 s
0/100
25%
Value16.2 s
0/100
10%
Value2,320 ms
5/100
30%
Value0.402
25/100
15%
Value16.4 s
5/100
10%
596 ms
123 ms
242 ms
241 ms
242 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 75% of them (40 requests) were addressed to the original Epoch.ua, 2% (1 request) were made to Yandex.st and 2% (1 request) were made to . The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Hutchinson-transmission.ru.
Page size can be reduced by 507.3 kB (20%)
2.5 MB
2.0 MB
In fact, the total size of Epoch.ua main page is 2.5 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 22.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. 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 22.4 kB or 78% of the original size.
Potential reduce by 155.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. Epoch images are well optimized though.
Potential reduce by 264.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 264.4 kB or 67% of the original size.
Potential reduce by 64.6 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. Epoch.ua needs all CSS files to be minified and compressed as it can save up to 64.6 kB or 81% of the original size.
Number of requests can be reduced by 24 (48%)
50
26
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epoch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
epoch.ua
596 ms
system.base.css
123 ms
system.menus.css
242 ms
system.messages.css
241 ms
system.theme.css
242 ms
calendar_multiday.css
243 ms
date.css
245 ms
field.css
244 ms
node.css
361 ms
search.css
358 ms
user.css
361 ms
views.css
363 ms
layout.css
363 ms
style.css
366 ms
print.css
476 ms
jquery.js
602 ms
jquery.once.js
478 ms
drupal.js
486 ms
ru_N8iS6zjYZO_f0vAZXVXY_9LF2-XRcc2xQVGcLMujhIc.js
835 ms
style.css
485 ms
style.css
592 ms
jquery.min.js
10 ms
style.css
596 ms
javascript;
2 ms
jquery.min.js
726 ms
jquery-ui.min.js
863 ms
jquery.spasticNav.js
709 ms
ofconf-pic452-452x452-10415.jpeg
744 ms
171050.jpg
705 ms
rh-hutchinson-transmission.jpg
1254 ms
Kak-priobresti-poleznyie-privyichki.jpg
762 ms
Weihnachten-Warum-feiern-wir.jpg
579 ms
398677.jpg
255 ms
main_pozirovanie-i-idei-dlya-novogodney-fotosessii-112.jpg
1070 ms
business-success11.jpg
878 ms
bg.jpg
724 ms
epoch.png
124 ms
rus.png
359 ms
eng.png
486 ms
germ.png
475 ms
feed.png
125 ms
grid16.png
481 ms
grid11.png
364 ms
grid14.png
481 ms
grid12.png
607 ms
grid15.png
715 ms
grid13.png
718 ms
pod.jpg
603 ms
Facebook.png
606 ms
linkedin.png
842 ms
analytics.js
395 ms
analytics.js
544 ms
o-proekte-slovo-bez-granic
398 ms
epoch.ua 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
button, link, and menuitem elements do not have accessible names.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Heading elements are not in a sequentially-descending order
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.
epoch.ua SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Epoch.ua 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 Epoch.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.
epoch.ua
Open Graph description is not detected on the main page of Epoch. 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: