Tools & Wizards About Us

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

pink.rs

pink.rs | Najbrži portal u Srbiji

Page Load Speed

6.6 sec in total

First Response

303 ms

Resources Loaded

5.1 sec

Page Rendered

1.1 sec

About Website

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

Najnovije današnje vesti iz zemlje, sveta, sporta, showbiza, zabave kao i zanimljivosti pratite na Pinku i pink.rs portalu.

Visit pink.rs

Key Findings

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

Performance Metrics

pink.rs performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value2,700 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.171

70/100

15%

TTI (Time to Interactive)

Value35.3 s

0/100

10%

Network Requests Diagram

pink.rs

303 ms

pink.rs

483 ms

bootstrap.min.css

123 ms

styles.css

197 ms

all.css

61 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 36% of them (44 requests) were addressed to the original Pink.rs, 46% (56 requests) were made to Media.pink.rs and 3% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Cdn.midas-network.com.

Page Optimization Overview & Recommendations

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

Content Size

2.9 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pink.rs main page is 2.9 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. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 165.2 kB

  • Original 184.6 kB
  • After minification 88.9 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 95.7 kB, which is 52% 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 165.2 kB or 90% of the original size.

Image Optimization

-7%

Potential reduce by 114.2 kB

  • Original 1.7 MB
  • After minification 1.6 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. Pink images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 288.6 kB

  • Original 763.3 kB
  • After minification 763.2 kB
  • After compression 474.6 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 288.6 kB or 38% of the original size.

CSS Optimization

-84%

Potential reduce by 191.4 kB

  • Original 227.3 kB
  • After minification 227.1 kB
  • After compression 35.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. Pink.rs needs all CSS files to be minified and compressed as it can save up to 191.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (21%)

Requests Now

115

After Optimization

91

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

pink.rs accessibility score

78

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Best Practices

pink.rs best practices score

67

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pink.rs SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    SR

  • Encoding

    UTF-8

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