Tools & Wizards About Us

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

gss.bg

:: Мобилни и настолни компютри, дентален софтуер, медицински системи

Page Load Speed

12.1 sec in total

First Response

3.2 sec

Resources Loaded

8.8 sec

Page Rendered

112 ms

About Website

Welcome to gss.bg homepage info - get ready to check Gss best content for Bulgaria right away, or after learning these important things about gss.bg

Всичко за Вашият компютър! Продажба и сервиз на преносими и настолни компютри,сървъри,софтуер и компоненти. Специализиран медицински софтуер - дентален, ПИМП и СИМП,лаборатория

Visit gss.bg

Key Findings

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

Performance Metrics

gss.bg performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

gss.bg

3219 ms

scripts.js

219 ms

overlib.js

690 ms

configurator.js

232 ms

cart.js

238 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 93% of them (40 requests) were addressed to the original Gss.bg, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Gss.bg.

Page Optimization Overview & Recommendations

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

Content Size

168.5 kB

After Optimization

104.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Gss.bg main page is 168.5 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. 15% of websites need less resources to load. Javascripts take 81.6 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 7.4 kB

  • Original 10.8 kB
  • After minification 9.6 kB
  • After compression 3.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 7.4 kB or 69% of the original size.

Image Optimization

-7%

Potential reduce by 5.4 kB

  • Original 76.1 kB
  • After minification 70.7 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. Gss images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 51.7 kB

  • Original 81.6 kB
  • After minification 63.1 kB
  • After compression 30.0 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 51.7 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (62%)

Requests Now

42

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gss. 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 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

gss.bg accessibility score

60

Accessibility Issues

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

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

Form elements do not have associated labels

Best Practices

gss.bg best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

gss.bg SEO score

62

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

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    BG

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gss.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 Gss.bg main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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