Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

sff.ba

Početna | Sarajevo Film Festival

Page Load Speed

3 sec in total

First Response

449 ms

Resources Loaded

2.3 sec

Page Rendered

257 ms

sff.ba screenshot

About Website

Click here to check amazing Sff content for Poland. Otherwise, check out these important facts you probably never knew about sff.ba

Visit sff.ba

Key Findings

We analyzed Sff.ba page load time and found that the first response time was 449 ms and then it took 2.5 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.

Performance Metrics

sff.ba performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.883

3/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

sff.ba

449 ms

index.php

541 ms

css

43 ms

bootstrap.css

267 ms

bootstrap-responsive.css

263 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 78% of them (32 requests) were addressed to the original Sff.ba, 7% (3 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (708 ms) belongs to the original domain Sff.ba.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.2 kB (27%)

Content Size

286.8 kB

After Optimization

208.7 kB

In fact, the total size of Sff.ba main page is 286.8 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. 35% of websites need less resources to load. Images take 207.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 21.4 kB

  • Original 27.0 kB
  • After minification 20.2 kB
  • After compression 5.6 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. This page needs HTML code to be minified as it can gain 6.8 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.4 kB or 79% of the original size.

Image Optimization

-12%

Potential reduce by 24.9 kB

  • Original 207.0 kB
  • After minification 182.1 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, Sff needs image optimization as it can save up to 24.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

34

After Optimization

24

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

Accessibility Review

sff.ba accessibility score

46

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sff.ba best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

sff.ba SEO score

77

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

Language and Encoding

  • Language Detected

    BS

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sff.ba can be misinterpreted by Google and other search engines. Our service has detected that 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 Sff.ba 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 Sff. 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: