Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

jasmin.rs

Jasmin parfimerije - ŠMINKA · PARFEMI · NEGA LICA · NEGA TELA

Page Load Speed

6.8 sec in total

First Response

837 ms

Resources Loaded

5.6 sec

Page Rendered

338 ms

jasmin.rs screenshot

About Website

Click here to check amazing Jasmin content for Serbia. Otherwise, check out these important facts you probably never knew about jasmin.rs

Online prodaja parfema, kozmetike, šminke... Preko 20.000 proizvoda u ponudi. Besplatna isporuka za porudžbine preko 3000 RSD - Jasmin parfimerije.

Visit jasmin.rs

Key Findings

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

Performance Metrics

jasmin.rs performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value37.3 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value4,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.562

12/100

15%

TTI (Time to Interactive)

Value21.4 s

1/100

10%

Network Requests Diagram

jasmin.rs

837 ms

style.css

234 ms

jasmin1.css

494 ms

shop.css

234 ms

jquery-1.8.2.min.js

465 ms

Our browser made a total of 204 requests to load all elements on the main page. We found that 96% of them (195 requests) were addressed to the original Jasmin.rs, 1% (2 requests) were made to Stats.g.doubleclick.net and 1% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Jasmin.rs.

Page Optimization Overview & Recommendations

Page size can be reduced by 518.3 kB (20%)

Content Size

2.6 MB

After Optimization

2.1 MB

In fact, the total size of Jasmin.rs main page is 2.6 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. 65% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 83.3 kB

  • Original 98.6 kB
  • After minification 97.9 kB
  • After compression 15.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 83.3 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 166.1 kB

  • Original 2.1 MB
  • After minification 2.0 MB

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. Jasmin images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 209.6 kB

  • Original 300.0 kB
  • After minification 235.9 kB
  • After compression 90.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 209.6 kB or 70% of the original size.

CSS Optimization

-80%

Potential reduce by 59.3 kB

  • Original 73.8 kB
  • After minification 55.3 kB
  • After compression 14.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. Jasmin.rs needs all CSS files to be minified and compressed as it can save up to 59.3 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (13%)

Requests Now

201

After Optimization

174

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

Accessibility Review

jasmin.rs accessibility score

77

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

jasmin.rs best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

jasmin.rs SEO score

80

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jasmin.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 Jasmin.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

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