4.4 sec in total
546 ms
3.6 sec
212 ms
Welcome to poizdato.net homepage info - get ready to check Poizdato best content for Ukraine right away, or after learning these important things about poizdato.net
Розклад руху поїздів, електричок та приміських поїздів в Україні на 2024 рік: пошук за маршрутом, за станціями; пасажирські, швидкі та приміські потяги; вокзали та станції.
Visit poizdato.netWe analyzed Poizdato.net page load time and found that the first response time was 546 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
poizdato.net performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value9.5 s
0/100
25%
Value6.6 s
37/100
10%
Value1,100 ms
23/100
30%
Value0.015
100/100
15%
Value12.8 s
13/100
10%
546 ms
99 ms
200 ms
291 ms
297 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 33% of them (43 requests) were addressed to the original Poizdato.net, 14% (18 requests) were made to Pagead2.googlesyndication.com and 11% (14 requests) were made to S0.2mdn.net. The less responsive or slowest element that took the longest time to load (821 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 192.6 kB (15%)
1.3 MB
1.1 MB
In fact, the total size of Poizdato.net main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 49.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. This page needs HTML code to be minified as it can gain 9.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 49.8 kB or 83% of the original size.
Potential reduce by 15.3 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. Poizdato images are well optimized though.
Potential reduce by 124.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 124.4 kB or 12% of the original size.
Potential reduce by 3.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. Poizdato.net needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 13% of the original size.
Number of requests can be reduced by 63 (62%)
102
39
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poizdato. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
poizdato.net
546 ms
bootstrap.min.css
99 ms
jquery-ui.css
200 ms
jquery.ui.timepicker.css
291 ms
style.css
297 ms
jquery.min.js
404 ms
jquery-ui.min.js
500 ms
jquery.ui.datepicker-ua.js
302 ms
jquery.tabslet.min.js
314 ms
jquery.ui.timepicker.js
485 ms
functions.js
394 ms
functions_not_ie.js
400 ms
helper.js
417 ms
js
60 ms
b6a03b3d-6691-47d1-9355-af550402c101.min.js
28 ms
adsbygoogle.js
59 ms
plugin.min.js
438 ms
logo_ua.png
260 ms
sky.jpg
242 ms
tab_shadow.png
110 ms
tabs_bg.jpg
111 ms
place.png
109 ms
reverce.png
112 ms
date.png
242 ms
find.png
242 ms
roboto-regular.woff
210 ms
roboto-medium.woff
286 ms
roboto-light.woff
345 ms
roboto-bold.woff
284 ms
roboto-black.woff
361 ms
info1.png
285 ms
info2.png
285 ms
info3.png
375 ms
info4.png
376 ms
logo2_ua.png
376 ms
slotcar_library.js
34 ms
show_ads_impl.js
164 ms
clock.png
322 ms
flag.png
379 ms
calendar.png
398 ms
train.png
404 ms
footer_bg.jpg
419 ms
tw.png
420 ms
social_base.png
419 ms
fb.png
476 ms
watch.js
4 ms
robotoslab-bold.woff
570 ms
robotoslab-regular.woff
483 ms
ui-bg_flat_75_ffffff_40x100.png
366 ms
zrt_lookup.html
56 ms
ads
821 ms
time.png
249 ms
ads
596 ms
ads
391 ms
ads
719 ms
gen_204
74 ms
pixel
27 ms
dv3.js
27 ms
window_focus.js
21 ms
qs_click_protection.js
26 ms
ufs_web_display.js
14 ms
pixel
44 ms
pixel
44 ms
ad
160 ms
rum
122 ms
pixel
120 ms
14763004658117789537
106 ms
load_preloaded_resource.js
181 ms
abg_lite.js
305 ms
2bbefa48e780f0171741373010dbd4b2.js
290 ms
icon.png
214 ms
rum
207 ms
bounce
204 ms
html_inpage_rendering_lib_200_280.js
289 ms
omrhp.js
194 ms
abg_lite.js
223 ms
Q12zgMmT.js
223 ms
pixel
198 ms
express_html_inpage_rendering_lib_200_280.js
255 ms
gen_204
145 ms
pixel
60 ms
css
145 ms
reactive_library.js
93 ms
activeview
176 ms
62bHydCX.html
94 ms
pixel
72 ms
pixel
72 ms
activeview
137 ms
setuid
71 ms
rum
72 ms
pixel
72 ms
activeview
291 ms
M3wb6Cd7vtj7C-F6LRKga9uye_tTOdO4SICydejC-uA.js
108 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
251 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
315 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
315 ms
rum
239 ms
s
226 ms
feedback_grey600_24dp.png
150 ms
fullscreen_api_adapter.js
149 ms
interstitial_ad_frame.js
148 ms
settings_grey600_24dp.png
153 ms
pixel
202 ms
gen_204
95 ms
activeview
95 ms
index.html
62 ms
fn0zdpJdGcA-2L7yJYd2Jn-5oFlF2Vy_IZ_dxNt8NnA.js
56 ms
160x600.html
62 ms
pixel
103 ms
um
389 ms
pixel
102 ms
Enabler_01_250.js
47 ms
css
136 ms
createjs_2019.11.15_min.js
103 ms
160x600.js
102 ms
um
322 ms
TravelSans-Regular.ttf
258 ms
TravelSans-Regular.woff
256 ms
TravelSans-Regular.ttf
258 ms
Lardent-SlabRegular-Pro.ttf
262 ms
Lardent-SlabRegular-Pro.woff
260 ms
Lardent-SlabRegular-Pro.ttf
262 ms
160x600_atlas_P_.png
240 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyzAFyo4d4k.ttf
199 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyzAFyo4d4k.ttf
198 ms
sodar
149 ms
firstevent
108 ms
pixel
35 ms
sd
34 ms
pixel
31 ms
sodar2.js
20 ms
poizdato.net 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.
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.
poizdato.net 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
Missing source maps for large first-party JavaScript
poizdato.net 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
UK
UK
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poizdato.net can be misinterpreted by Google and other search engines. Our service has detected that Ukrainian is used on the page, and it matches the claimed language. Our system also found out that Poizdato.net 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.
poizdato.net
Open Graph description is not detected on the main page of Poizdato. 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: