Tools & Wizards About Us
jolly.rs screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

jolly.rs

Jolly Holidays - Turistička agencija - Jolly Holidays

Page Load Speed

4.9 sec in total

First Response

1.4 sec

Resources Loaded

3.3 sec

Page Rendered

191 ms

jolly.rs screenshot

About Website

Visit jolly.rs now to see the best up-to-date Jolly content for Serbia and also check out these interesting facts you probably never knew about jolly.rs

Jolly Holidays - Letovanje 2016 - Zimovanje - Metropole - Daleke destinacije - Krstarenja - Egipat - Emirati - Dubai

Visit jolly.rs

Key Findings

We analyzed Jolly.rs page load time and found that the first response time was 1.4 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

jolly.rs performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.242

51/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

jolly.rs

1360 ms

simple-line-icons.css

50 ms

k2.css

236 ms

widgetkit-e9283f0d.css

474 ms

jcemediabox.css

240 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 67% of them (65 requests) were addressed to the original Jolly.rs, 20% (19 requests) were made to Fonts.gstatic.com and 8% (8 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Jolly.rs.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (56%)

Content Size

2.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jolly.rs main page is 2.7 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. 75% 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. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 29.8 kB

  • Original 37.5 kB
  • After minification 35.8 kB
  • After compression 7.7 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 29.8 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 521 B

  • Original 745.7 kB
  • After minification 745.2 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. Jolly images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 856.9 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 327.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 856.9 kB or 72% of the original size.

CSS Optimization

-86%

Potential reduce by 635.1 kB

  • Original 737.9 kB
  • After minification 662.7 kB
  • After compression 102.8 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. Jolly.rs needs all CSS files to be minified and compressed as it can save up to 635.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (73%)

Requests Now

73

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jolly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

jolly.rs

jolly.rs

1360 ms

simple-line-icons.css

simple-line-icons.css

50 ms

k2.css

k2.css

236 ms

widgetkit-e9283f0d.css

widgetkit-e9283f0d.css

474 ms

jcemediabox.css

jcemediabox.css

240 ms

style.css

style.css

238 ms

rokbox.css

rokbox.css

360 ms

css

css

27 ms

css

css

43 ms

css

css

47 ms

bootstrap.min.css

bootstrap.min.css

595 ms

font-awesome.min.css

font-awesome.min.css

354 ms

venobox.css

venobox.css

357 ms

template.css

template.css

954 ms

preset1.css

preset1.css

475 ms

frontend-edit.css

frontend-edit.css

478 ms

font-awesome.css

font-awesome.css

479 ms

font-socialico.css

font-socialico.css

588 ms

shortcodes.css

shortcodes.css

711 ms

product.css

product.css

590 ms

settings.css

settings.css

599 ms

dynamic-captions.css

dynamic-captions.css

707 ms

static-captions.css

static-captions.css

708 ms

jquery.min.js

jquery.min.js

830 ms

jquery-noconflict.js

jquery-noconflict.js

712 ms

jquery-migrate.min.js

jquery-migrate.min.js

824 ms

k2.frontend.js

k2.frontend.js

826 ms

caption.js

caption.js

827 ms

widgetkit-6f3bfeaf.js

widgetkit-6f3bfeaf.js

832 ms

jcemediabox.js

jcemediabox.js

1060 ms

core.js

core.js

943 ms

mootools-core.js

mootools-core.js

1065 ms

mootools-more.js

mootools-more.js

1305 ms

rokbox.js

rokbox.js

1078 ms

bootstrap.min.js

bootstrap.min.js

1179 ms

jquery.sticky.js

jquery.sticky.js

1078 ms

main.js

main.js

1177 ms

venobox.min.js

venobox.min.js

1184 ms

frontend-edit.js

frontend-edit.js

1186 ms

shortcodes.js

shortcodes.js

1189 ms

js

js

59 ms

css

css

21 ms

css

css

18 ms

css

css

23 ms

css

css

25 ms

css

css

22 ms

mootools-mobile.js

mootools-mobile.js

1191 ms

rokmediaqueries.js

rokmediaqueries.js

1074 ms

roksprocket.js

roksprocket.js

1118 ms

moofx.js

moofx.js

1118 ms

roksprocket.request.js

roksprocket.request.js

1006 ms

tables.js

tables.js

1065 ms

tables-speeds.js

tables-speeds.js

1067 ms

ajax_1.5.pack.js

ajax_1.5.pack.js

956 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

1014 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1022 ms

lightbox.js

lightbox.js

515 ms

mediaelement-and-player.js

mediaelement-and-player.js

725 ms

spotlight.js

spotlight.js

702 ms

jollylogo.png

jollylogo.png

270 ms

jollylogo2.jpg

jollylogo2.jpg

264 ms

logo-jolly.png

logo-jolly.png

265 ms

splendid.jpg

splendid.jpg

269 ms

srbija.jpg

srbija.jpg

386 ms

wellness.jpg

wellness.jpg

388 ms

egipat.jpg

egipat.jpg

388 ms

rim.jpg

rim.jpg

505 ms

generali.jpg

generali.jpg

387 ms

avio.jpg

avio.jpg

386 ms

js

js

171 ms

analytics.js

analytics.js

192 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

160 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

165 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

160 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

164 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

164 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

164 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

163 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

181 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

188 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

188 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

409 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

433 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwpmPg.ttf

219 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwpmPg.ttf

188 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwpmPg.ttf

183 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4tM3OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4tM3OwpmPg.ttf

188 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM2OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM2OwpmPg.ttf

221 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4o0wOwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4o0wOwpmPg.ttf

397 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwpmPg.ttf

221 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4tMwOwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4tMwOwpmPg.ttf

219 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4vowOwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4vowOwpmPg.ttf

300 ms

popup.html

popup.html

279 ms

tooltip.html

tooltip.html

280 ms

timer.png

timer.png

271 ms

loader.gif

loader.gif

370 ms

collect

collect

86 ms

Accessibility Review

jolly.rs accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

jolly.rs best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

jolly.rs SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    SR

  • Language Claimed

    SR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jolly.rs can be misinterpreted by Google and other search engines. Our service has detected that Serbian is used on the page, and it matches the claimed language. Our system also found out that Jolly.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.

Social Sharing Optimization

jolly.rs

Open Graph description is not detected on the main page of Jolly. 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: