1.6 sec in total
251 ms
1.2 sec
105 ms
Click here to check amazing FORTRESS content for Serbia. Otherwise, check out these important facts you probably never knew about fortress.rs
Visit fortress.rsWe analyzed Fortress.rs page load time and found that the first response time was 251 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
fortress.rs performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value8.6 s
2/100
25%
Value8.1 s
21/100
10%
Value60 ms
100/100
30%
Value0
100/100
15%
Value8.7 s
37/100
10%
251 ms
244 ms
610 ms
45 ms
58 ms
Our browser made a total of 15 requests to load all elements on the main page. We found that 27% of them (4 requests) were addressed to the original Fortress.rs, 33% (5 requests) were made to Gstatic.com and 20% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (610 ms) belongs to the original domain Fortress.rs.
Page size can be reduced by 216.8 kB (62%)
348.5 kB
131.8 kB
In fact, the total size of Fortress.rs main page is 348.5 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. Only 5% of websites need less resources to load. Javascripts take 300.4 kB which makes up the majority of the site volume.
Potential reduce by 1.0 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 1.0 kB or 58% of the original size.
Potential reduce by 8.6 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, FORTRESS needs image optimization as it can save up to 8.6 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 200.7 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 200.7 kB or 67% of the original size.
Potential reduce by 6.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. Fortress.rs needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 76% of the original size.
We found no issues to fix!
12
12
The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FORTRESS. According to our analytics all requests are already optimized.
fortress.rs
251 ms
styleIn.css
244 ms
jquery-1.11.2.min.js
610 ms
api.js
45 ms
recaptcha__en.js
58 ms
shieldicon.png
363 ms
fallback
28 ms
fallback__ltr.css
8 ms
payload
13 ms
css
56 ms
logo_48.png
14 ms
refresh.png
20 ms
audio.png
30 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
53 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
64 ms
fortress.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
Form elements do not have associated labels
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.
fortress.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
Registers an unload listener
Detected JavaScript libraries
Page has valid source maps
fortress.rs SEO score
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 doesn't use legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fortress.rs can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fortress.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.
fortress.rs
Open Graph description is not detected on the main page of FORTRESS. 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: