5.7 sec in total
216 ms
5.4 sec
100 ms
Visit eway.ua now to see the best up-to-date Eway content and also check out these interesting facts you probably never knew about eway.ua
Актуальна карта маршруток Києва, пошук маршрутів з А в Б, карта маршрутів громадського транспорту Києва, Android и Iphone додаток, віджет для сайту.
Visit eway.uaWe analyzed Eway.ua page load time and found that the first response time was 216 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eway.ua performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value19.8 s
0/100
25%
Value15.0 s
1/100
10%
Value4,990 ms
0/100
30%
Value0.163
72/100
15%
Value29.8 s
0/100
10%
216 ms
314 ms
168 ms
593 ms
615 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Eway.ua, 37% (17 requests) were made to Static.easyway.info and 13% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Vtiles.easyway.info.
Page size can be reduced by 266.2 kB (64%)
416.0 kB
149.8 kB
In fact, the total size of Eway.ua main page is 416.0 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. 60% of websites need less resources to load. HTML takes 279.8 kB which makes up the majority of the site volume.
Potential reduce by 263.1 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 263.1 kB or 94% of the original size.
Potential reduce by 1.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. Obviously, Eway needs image optimization as it can save up to 1.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 86 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 1.5 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. Eway.ua has all CSS files already compressed.
Number of requests can be reduced by 25 (68%)
37
12
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eway. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eway.ua
216 ms
www.eway.in.ua
314 ms
kyiv
168 ms
leaflet.css
593 ms
mapbox-gl.css
615 ms
2.css
704 ms
css2
108 ms
google-protobuf.js
1089 ms
eventsource.min.js
598 ms
lz-string.min.js
602 ms
leaflet.js
911 ms
mapbox-gl.js
1411 ms
leaflet-mapbox-gl.js
616 ms
leaflet-smooth-wheel-zoom.js
617 ms
1.js
882 ms
2.js
1289 ms
adsbygoogle.js
160 ms
1.css
101 ms
gtm.js
306 ms
android-small.png
281 ms
apple-small.png
270 ms
header_logo.png
272 ms
arrow-down-white.png
270 ms
facebook.png
268 ms
twitter.png
270 ms
ua.png
1146 ms
zrt_lookup.html
959 ms
show_ads_impl.js
954 ms
all.js
842 ms
alerts
508 ms
user-account.svg
290 ms
analytics.js
305 ms
KFOmCnqEu92Fr1Me5Q.ttf
531 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
525 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
521 ms
KFOkCnqEu92Fr1MmgWxP.ttf
579 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
524 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
527 ms
all.js
344 ms
cookie.js
386 ms
integrator.js
361 ms
ads
654 ms
collect
123 ms
228 ms
collect
142 ms
ga-audiences
57 ms
eway.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
[aria-*] attributes do not match their roles
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
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
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>).
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.
eway.ua best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
eway.ua 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
UK
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eway.ua can be misinterpreted by Google and other search engines. Our service has detected that Ukrainian 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 Eway.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.
eway.ua
Open Graph data is detected on the main page of Eway. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: