7.7 sec in total
532 ms
6.9 sec
322 ms
Visit port.rs now to see the best up-to-date Port content for Serbia and also check out these interesting facts you probably never knew about port.rs
This domain may be for sale!
Visit port.rsWe analyzed Port.rs page load time and found that the first response time was 532 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
port.rs performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value3.3 s
69/100
25%
Value2.9 s
95/100
10%
Value80 ms
99/100
30%
Value0.22
57/100
15%
Value3.2 s
94/100
10%
532 ms
374 ms
1028 ms
507 ms
2060 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Port.rs, 55% (40 requests) were made to Media.port-network.com and 10% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Ad.adverticum.net.
Page size can be reduced by 208.8 kB (43%)
490.9 kB
282.1 kB
In fact, the total size of Port.rs main page is 490.9 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. 50% of websites need less resources to load. Images take 204.6 kB which makes up the majority of the site volume.
Potential reduce by 105.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. 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 105.5 kB or 86% of the original size.
Potential reduce by 22.7 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, Port needs image optimization as it can save up to 22.7 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 72.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 72.4 kB or 47% of the original size.
Potential reduce by 8.2 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. Port.rs needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 76% of the original size.
Number of requests can be reduced by 25 (35%)
71
46
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Port. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
port.rs
532 ms
floatbox.css
374 ms
floatbox.js
1028 ms
html_elements.print_stylesheets
507 ms
html_elements.print_scripts
2060 ms
carousel.css
372 ms
hmapxy.js
393 ms
goa3.js
652 ms
options.js
132 ms
port_rs_logo.png
212 ms
837589_3.jpg
213 ms
t.gif
213 ms
679297_3.jpg
267 ms
813490_3.jpg
269 ms
848763_3.jpg
521 ms
784115_3.jpg
449 ms
848766_3.jpg
271 ms
808287_3.jpg
423 ms
836701_3.jpg
389 ms
6050027_7.gif
392 ms
6050028_7.gif
391 ms
5000004_7.gif
519 ms
6027299_7.gif
520 ms
6021075_7.gif
521 ms
6049256_7.gif
553 ms
6042004_7.gif
578 ms
6019397_7.gif
649 ms
6036771_7.gif
811 ms
6047806_7.gif
649 ms
6040176_7.gif
651 ms
ad_rs.png
675 ms
lmbg.png
700 ms
iconset.png
757 ms
493142_22.jpg
758 ms
arrow_32_22.jpg
890 ms
280144_22.jpg
792 ms
810463_21.jpg
855 ms
footerbg.png
856 ms
ga.js
26 ms
__utm.gif
89 ms
xgemius.js
466 ms
core_572.js
887 ms
authentication.ajax_header_stripe
141 ms
detect.js
138 ms
arrow_left_gray.png
734 ms
arrow_right.png
737 ms
facebook.svg
694 ms
googleplus.svg
1222 ms
user.png
721 ms
fpdata.js
117 ms
lsget.html
252 ms
rexdot.js
116 ms
z
280 ms
adsbygoogle.js
19 ms
port_network_728x90_SRB.png
2633 ms
adsbygoogle.js
32 ms
ca-pub-3162003988933436.js
49 ms
zrt_lookup.html
39 ms
show_ads_impl.js
60 ms
ads
255 ms
osd.js
11 ms
ads
210 ms
17809810772746321655
36 ms
abg.js
35 ms
m_js_controller.js
55 ms
googlelogo_color_112x36dp.png
117 ms
9976730299599428719
53 ms
s
35 ms
x_button_blue2.png
39 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
2 ms
activeview
13 ms
ui
30 ms
blank.gif
132 ms
port.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.
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
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
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.
port.rs best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
port.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
SR
ISO-8859-2
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Port.rs can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Serbian language. Our system also found out that Port.rs main page’s claimed encoding is iso-8859-2. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
port.rs
Open Graph description is not detected on the main page of Port. 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: