2.9 sec in total
149 ms
2.7 sec
66 ms
Visit eway.rs now to see the best up-to-date Eway content for Serbia and also check out these interesting facts you probably never knew about eway.rs
EasyWay will help you get to your destination by using Beograd public transport (bus, trolleybus, metro, tram)
Visit eway.rsWe analyzed Eway.rs page load time and found that the first response time was 149 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
eway.rs performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value10.2 s
0/100
25%
Value9.9 s
10/100
10%
Value3,150 ms
2/100
30%
Value0.21
59/100
15%
Value15.1 s
7/100
10%
149 ms
435 ms
132 ms
49 ms
77 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 8% of them (5 requests) were addressed to the original Eway.rs, 68% (45 requests) were made to Static.easyway.info and 9% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (769 ms) belongs to the original domain Eway.rs.
Page size can be reduced by 32.3 kB (11%)
299.4 kB
267.1 kB
In fact, the total size of Eway.rs main page is 299.4 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. 65% of websites need less resources to load. Javascripts take 199.2 kB which makes up the majority of the site volume.
Potential reduce by 22.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. This page needs HTML code to be minified as it can gain 3.5 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 22.5 kB or 78% of the original size.
Potential reduce by 8.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. Obviously, Eway needs image optimization as it can save up to 8.3 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 0 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.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. Eway.rs has all CSS files already compressed.
Number of requests can be reduced by 41 (72%)
57
16
The browser has sent 57 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 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eway.rs
149 ms
eway.rs
435 ms
beograd
132 ms
leaflet.css
49 ms
mapbox-gl.css
77 ms
2.css
60 ms
css2
38 ms
google-protobuf.js
74 ms
eventsource.min.js
81 ms
lz-string.min.js
87 ms
leaflet.js
86 ms
mapbox-gl.js
90 ms
leaflet-mapbox-gl.js
93 ms
leaflet-smooth-wheel-zoom.js
90 ms
1.js
86 ms
2.js
87 ms
gpt.js
47 ms
1.css
20 ms
gtm.js
668 ms
alerts
183 ms
routes
769 ms
android-small.png
127 ms
apple-small.png
50 ms
header_logo.png
51 ms
arrow-down-white.png
50 ms
user-account.svg
131 ms
rs.png
181 ms
pubads_impl.js
20 ms
KFOmCnqEu92Fr1Me5Q.ttf
101 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
127 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
150 ms
KFOkCnqEu92Fr1MmgWxP.ttf
150 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
151 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
152 ms
22665415972
178 ms
grey-cross.png
178 ms
nearby_address_search.png
178 ms
swap_points.png
179 ms
compile_inactive.png
177 ms
compile_address_search_a_free.png
176 ms
compile_address_search_b_free.png
179 ms
erase.png
241 ms
bus_active.png
248 ms
tram_active.png
250 ms
trol_active.png
246 ms
boat_active.png
253 ms
train_active.png
258 ms
walk_ways_free.png
348 ms
optimal_free.png
351 ms
cheap_free.png
356 ms
fast_free.png
357 ms
result_bg.png
362 ms
grey-cross.png
368 ms
link-inactive.png
453 ms
ajax_loader.gif
463 ms
attention-sign-small.png
466 ms
bg-left.png
467 ms
bg.png
675 ms
select_route_arrow.png
476 ms
stops-active.png
562 ms
places-inactive.png
753 ms
gps-active.png
569 ms
arrow.png
572 ms
restore-bounds.png
586 ms
bg-right.png
676 ms
js
46 ms
eway.rs 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.
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
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
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.rs best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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.rs 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eway.rs can be misinterpreted by Google and other search engines. Our service has detected that English 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.rs 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.rs
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: