Tools & Wizards About Us
npss.bg screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

npss.bg

НПСС | Национално представителство на студентските съвети в Република България

Page Load Speed

4.6 sec in total

First Response

803 ms

Resources Loaded

3.3 sec

Page Rendered

448 ms

npss.bg screenshot

About Website

Click here to check amazing Npss content. Otherwise, check out these important facts you probably never knew about npss.bg

НПСС България | Национално представителство на студентските съвети е единственото най-голямо представителство на студентската младеж в България. НПСС е член на ESU - Европейския студентски съюз.

Visit npss.bg

Key Findings

We analyzed Npss.bg page load time and found that the first response time was 803 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

npss.bg performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.3 s

0/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.141

78/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

npss.bg

803 ms

style.css

343 ms

superfish.css

344 ms

event_template.css

350 ms

responsive.css

352 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 88% of them (49 requests) were addressed to the original Npss.bg, 4% (2 requests) were made to Platform.twitter.com and 4% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Npss.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (58%)

Content Size

3.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 50.8 kB

  • Original 63.7 kB
  • After minification 62.3 kB
  • After compression 12.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. 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 50.8 kB or 80% of the original size.

Image Optimization

-50%

Potential reduce by 1.3 MB

  • Original 2.6 MB
  • After minification 1.3 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. Obviously, Npss needs image optimization as it can save up to 1.3 MB or 50% 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 306.7 kB

  • Original 515.0 kB
  • After minification 490.6 kB
  • After compression 208.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 306.7 kB or 60% of the original size.

CSS Optimization

-87%

Potential reduce by 579.2 kB

  • Original 665.0 kB
  • After minification 501.4 kB
  • After compression 85.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. Npss.bg needs all CSS files to be minified and compressed as it can save up to 579.2 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

53

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

npss.bg

npss.bg

803 ms

style.css

style.css

343 ms

superfish.css

superfish.css

344 ms

event_template.css

event_template.css

350 ms

responsive.css

responsive.css

352 ms

content.min.css

content.min.css

354 ms

jquery.min.js

jquery.min.js

591 ms

jquery-noconflict.js

jquery-noconflict.js

456 ms

jquery-migrate.min.js

jquery-migrate.min.js

457 ms

k2.frontend.js

k2.frontend.js

467 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

584 ms

jquery.ba-bbq.min.js

jquery.ba-bbq.min.js

472 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

682 ms

jquery.ui.tabs.js

jquery.ui.tabs.js

687 ms

timetable.js

timetable.js

585 ms

bootstrap.min.js

bootstrap.min.js

708 ms

core.js

core.js

702 ms

keepalive.js

keepalive.js

703 ms

bootstrap.css

bootstrap.css

945 ms

plyr.css

plyr.css

797 ms

theme.css

theme.css

1252 ms

custom.css

custom.css

821 ms

uikit.js

uikit.js

823 ms

uikit-core-components.js

uikit-core-components.js

943 ms

social.js

social.js

910 ms

plyr.js

plyr.js

1055 ms

theme.js

theme.js

942 ms

widgets.js

widgets.js

153 ms

plusone.js

plusone.js

82 ms

sdk.js

sdk.js

93 ms

notebook.png

notebook.png

147 ms

logon.png

logon.png

163 ms

right.png

right.png

144 ms

ESU1.png

ESU1.png

162 ms

01.jpg

01.jpg

706 ms

02.jpg

02.jpg

497 ms

03.jpg

03.jpg

260 ms

os.jpg

os.jpg

383 ms

student2019.png

student2019.png

385 ms

winter2019.png

winter2019.png

733 ms

su2019.png

su2019.png

380 ms

2024_vote.png

2024_vote.png

494 ms

PRAVILNIK.png

PRAVILNIK.png

501 ms

tab-nasc.png

tab-nasc.png

503 ms

tab-nasc0.png

tab-nasc0.png

609 ms

tab-nasc1.png

tab-nasc1.png

615 ms

content-10.jpg

content-10.jpg

737 ms

nsd3.png

nsd3.png

622 ms

nasc.png

nasc.png

724 ms

icon.png

icon.png

735 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

739 ms

gravity-icons.woff

gravity-icons.woff

817 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

sdk.js

sdk.js

19 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

51 ms

settings

settings

94 ms

Accessibility Review

npss.bg accessibility score

89

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.

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

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

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

Best Practices

npss.bg 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

SEO Factors

npss.bg 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

High

Page is blocked from indexing

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

    BG

  • Language Claimed

    BG

  • Encoding

    UTF-8

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

npss.bg

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