8.4 sec in total
982 ms
4.6 sec
2.8 sec
Click here to check amazing Fudeks content for Serbia. Otherwise, check out these important facts you probably never knew about fudeks.rs
Kompanija Fudeks pruža usluge prevoza u međunarodnom linijskom saobraćaju. Naši autobusi redovno saobraćaju prema Parizu, Beču, Trstu, Mestreu, Bolonji, Vićenci, Firenci, Cirihu, Budimpešti, Skoplju. ...
Visit fudeks.rsWe analyzed Fudeks.rs page load time and found that the first response time was 982 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fudeks.rs performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value12.9 s
0/100
25%
Value4.6 s
70/100
10%
Value340 ms
74/100
30%
Value0.246
50/100
15%
Value9.8 s
27/100
10%
982 ms
170 ms
179 ms
175 ms
181 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 58% of them (66 requests) were addressed to the original Fudeks.rs, 27% (31 requests) were made to Maps.google.com and 8% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Fudeks.rs.
Page size can be reduced by 1.5 MB (14%)
10.9 MB
9.3 MB
In fact, the total size of Fudeks.rs main page is 10.9 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. Images take 8.9 MB which makes up the majority of the site volume.
Potential reduce by 103.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 103.1 kB or 85% of the original size.
Potential reduce by 37.8 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. Fudeks images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 74% of the original size.
Potential reduce by 337.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. Fudeks.rs needs all CSS files to be minified and compressed as it can save up to 337.6 kB or 86% of the original size.
Number of requests can be reduced by 49 (50%)
98
49
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fudeks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.fudeks.rs
982 ms
wp-emoji-release.min.js
170 ms
js_composer_front.css
179 ms
styles.css
175 ms
checkbox.min.css
181 ms
rgs.css
180 ms
font-awesome.min.css
182 ms
steadysets.css
248 ms
linecon.css
250 ms
style.css
448 ms
responsive.css
279 ms
form.min.css
286 ms
jquery.js
408 ms
jquery-migrate.min.js
329 ms
modernizr.js
329 ms
core.min.js
310 ms
widget.min.js
310 ms
position.min.js
353 ms
menu.min.js
354 ms
autocomplete.min.js
528 ms
wpss-search-suggest.js
529 ms
jquery.form.min.js
532 ms
scripts.js
530 ms
superfish.js
529 ms
respond.js
532 ms
sticky.js
532 ms
prettyPhoto.js
532 ms
jquery.flexslider-min.js
533 ms
isotope.min.js
532 ms
carouFredSel.min.js
573 ms
appear.js
574 ms
init.js
852 ms
nectar-slider.js
692 ms
nectar-love.js
621 ms
js_composer_front.js
622 ms
wp-embed.min.js
625 ms
parallax.js
628 ms
map.js
571 ms
placeholders.min.js
637 ms
logo-1.png
981 ms
diagonal_line.png
317 ms
nectar-loading.gif
309 ms
venice-m.jpg
1578 ms
belvedere-m.jpg
1135 ms
budapest-m.jpg
1088 ms
perast-in-kotor-bay-montenegro-m.jpg
2297 ms
the-new-look-of-skopje-city-macedonia-m.jpg
1086 ms
www.fudeks.rs
1253 ms
HM-Logo1.png
1180 ms
Coca-Cola_logo.png
1179 ms
telenor1.png
1251 ms
siemens1.png
1254 ms
Vipnet_logo1.png
1288 ms
OpenSans-Regular-webfont.woff
1198 ms
OpenSans-Regular-webfont.woff
1338 ms
OpenSans-Semibold-webfont.woff
1339 ms
OpenSans-Semibold-webfont.woff
1468 ms
OpenSans-Light-webfont.woff
1468 ms
OpenSans-Light-webfont.woff
1467 ms
OpenSans-Bold-webfont.woff
1468 ms
OpenSansBold-webfont.woff
1472 ms
fontawesome-webfont.svg
1646 ms
icomoon.woff
1472 ms
js
109 ms
paris-m.jpg
1294 ms
grid.png
772 ms
common.js
47 ms
map.js
48 ms
util.js
41 ms
onion.js
40 ms
openhand_8_8.cur
205 ms
stats.js
27 ms
controls.js
32 ms
ViewportInfoService.GetViewportInfo
282 ms
transparent.png
47 ms
css
193 ms
google4.png
71 ms
mapcnt6.png
126 ms
sv5.png
147 ms
tmapctrl.png
46 ms
tmapctrl4.png
56 ms
google_white5.png
56 ms
fontawesome-webfont.woff
134 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
57 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
79 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
128 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
128 ms
vt
122 ms
vt
107 ms
vt
110 ms
vt
108 ms
vt
109 ms
vt
108 ms
vt
169 ms
vt
171 ms
vt
171 ms
vt
168 ms
vt
171 ms
vt
168 ms
vt
171 ms
vt
172 ms
vt
179 ms
vt
172 ms
vt
180 ms
vt
172 ms
vt
180 ms
vt
198 ms
vt
201 ms
vt
263 ms
marker.js
5 ms
AuthenticationService.Authenticate
208 ms
spotlight-poi.png
12 ms
infowindow.js
4 ms
fudeks.rs 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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields 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.
[aria-*] attributes do not have valid values
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
Form elements do not have associated labels
Links do not have a discernible name
fudeks.rs 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
fudeks.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
Tap targets are not sized appropriately
SR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fudeks.rs can be misinterpreted by Google and other search engines. Our service has detected that Serbian is used on the page, and it does not match the claimed English language. Our system also found out that Fudeks.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.
fudeks.rs
Open Graph data is detected on the main page of Fudeks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: