Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

gsp.rs

ГСП Београд

Page Load Speed

13.9 sec in total

First Response

1.1 sec

Resources Loaded

4.4 sec

Page Rendered

8.4 sec

gsp.rs screenshot

About Website

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

JKP Gradsko saobraćajno preduzeće GSP Beograd red voznje

Visit gsp.rs

Key Findings

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

Performance Metrics

gsp.rs performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

gsp.rs

1085 ms

naslovna.aspx

616 ms

style.css

369 ms

jquery.lightbox-0.5.css

301 ms

jquery-1.10.1.min.js

912 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to Gsp.rs and no external sources were called. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Gsp.rs.

Page Optimization Overview & Recommendations

Page size can be reduced by 606.0 kB (38%)

Content Size

1.6 MB

After Optimization

976.0 kB

In fact, the total size of Gsp.rs main page is 1.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. 50% of websites need less resources to load. Images take 959.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 40.8 kB

  • Original 48.7 kB
  • After minification 25.2 kB
  • After compression 7.9 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 23.5 kB, which is 48% 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 40.8 kB or 84% of the original size.

Image Optimization

-15%

Potential reduce by 141.6 kB

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

JavaScript Optimization

-67%

Potential reduce by 216.7 kB

  • Original 325.0 kB
  • After minification 318.8 kB
  • After compression 108.3 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 216.7 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 206.8 kB

  • Original 249.0 kB
  • After minification 247.4 kB
  • After compression 42.2 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. Gsp.rs needs all CSS files to be minified and compressed as it can save up to 206.8 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gsp. According to our analytics all requests are already optimized.

Accessibility Review

gsp.rs accessibility score

53

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

gsp.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

SEO Factors

gsp.rs SEO score

82

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 Gsp.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 Gsp.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 Gsp. 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: