2.8 sec in total
459 ms
2.1 sec
185 ms
Welcome to present.rs homepage info - get ready to check Present best content right away, or after learning these important things about present.rs
Visit present.rsWe analyzed Present.rs page load time and found that the first response time was 459 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
present.rs performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value12.4 s
0/100
25%
Value10.0 s
9/100
10%
Value50 ms
100/100
30%
Value0.009
100/100
15%
Value8.3 s
40/100
10%
459 ms
404 ms
206 ms
308 ms
220 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that all of those requests were addressed to Present.rs and no external sources were called. The less responsive or slowest element that took the longest time to load (719 ms) belongs to the original domain Present.rs.
Page size can be reduced by 110.9 kB (43%)
255.7 kB
144.8 kB
In fact, the total size of Present.rs main page is 255.7 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. 15% of websites need less resources to load. Images take 124.8 kB which makes up the majority of the site volume.
Potential reduce by 3.3 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 3.3 kB or 67% of the original size.
Potential reduce by 2.9 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. Present images are well optimized though.
Potential reduce by 94.8 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 94.8 kB or 83% of the original size.
Potential reduce by 9.9 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. Present.rs needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 80% of the original size.
Number of requests can be reduced by 10 (42%)
24
14
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Present. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
present.rs
459 ms
prototype.js
404 ms
scriptaculous.js
206 ms
lightbox.js
308 ms
lightbox.css
220 ms
AC_RunActiveContent.js
221 ms
glavni.css
218 ms
effects.js
314 ms
background.jpg
321 ms
spacer.gif
229 ms
2920875331_12ebf32a40_o.jpg
239 ms
390385084_c4ec1e4f0b.jpg
317 ms
996196_73564194.jpg
319 ms
logo.png
351 ms
Bspacer.png
426 ms
nav_devider.png
435 ms
bg.jpg
524 ms
inner_shaddow.png
516 ms
Wspacer.png
544 ms
17-1.gif
557 ms
senka.png
640 ms
senkaR.png
665 ms
logo_03.gif
719 ms
loading.gif
115 ms
closelabel.gif
212 ms
present.rs accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
present.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
Browser errors were logged to the console
Page has valid source maps
present.rs SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Present.rs can be misinterpreted by Google and other search engines. Our service has detected that Serbian 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 Present.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.
present.rs
Open Graph description is not detected on the main page of Present. 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: