Tools & Wizards About Us
test.bg screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

test.bg

TEST.BG - национален сертификационен център, безплатни тестове и сертификация

Page Load Speed

4 sec in total

First Response

260 ms

Resources Loaded

3.3 sec

Page Rendered

518 ms

test.bg screenshot

About Website

Click here to check amazing TEST content for Bulgaria. Otherwise, check out these important facts you probably never knew about test.bg

TEST.BG е най-големият в България тестов център с вече над 70 000 потребители! Той предлага на своите членове възможност за безплатно явяване на изпит на едни от най-търсените доставчици в световен ма...

Visit test.bg

Key Findings

We analyzed Test.bg page load time and found that the first response time was 260 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

test.bg performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

test.bg

260 ms

www.test.bg

820 ms

js

64 ms

jquery-3.3.1.min.js

233 ms

popper.min.js

342 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 70% of them (49 requests) were addressed to the original Test.bg, 19% (13 requests) were made to Embed.tawk.to and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (820 ms) belongs to the original domain Test.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 486.1 kB (13%)

Content Size

3.7 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Test.bg main page is 3.7 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 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-96%

Potential reduce by 414.6 kB

  • Original 432.9 kB
  • After minification 212.5 kB
  • After compression 18.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 220.4 kB, which is 51% 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 414.6 kB or 96% of the original size.

Image Optimization

-2%

Potential reduce by 45.6 kB

  • Original 2.9 MB
  • After minification 2.9 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. TEST images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 24.1 kB

  • Original 274.5 kB
  • After minification 274.5 kB
  • After compression 250.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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 1.8 kB

  • Original 43.8 kB
  • After minification 43.7 kB
  • After compression 42.0 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. Test.bg has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (57%)

Requests Now

65

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

test.bg

test.bg

260 ms

www.test.bg

www.test.bg

820 ms

js

js

64 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

233 ms

popper.min.js

popper.min.js

342 ms

bootstrap.min.js

bootstrap.min.js

455 ms

switchery.min.js

switchery.min.js

345 ms

icheck.min.js

icheck.min.js

347 ms

js.cookie.js

js.cookie.js

397 ms

jquery.datetimepicker.full.min.js

jquery.datetimepicker.full.min.js

462 ms

functions.js

functions.js

462 ms

css

css

39 ms

bootstrap.min.css

bootstrap.min.css

482 ms

fontawesome-all.min.css

fontawesome-all.min.css

512 ms

switchery.min.css

switchery.min.css

567 ms

all.css

all.css

567 ms

jquery.datetimepicker.min.css

jquery.datetimepicker.min.css

569 ms

style.css

style.css

575 ms

js

js

47 ms

analytics.js

analytics.js

23 ms

collect

collect

52 ms

logo.png

logo.png

150 ms

pearson-logo.png

pearson-logo.png

203 ms

logo.png

logo.png

316 ms

pearson-vue-white-bg.png

pearson-vue-white-bg.png

204 ms

en.png

en.png

213 ms

fr.png

fr.png

263 ms

de.png

de.png

315 ms

es.png

es.png

316 ms

it.png

it.png

325 ms

os.png

os.png

357 ms

office.png

office.png

377 ms

internet-and-web.png

internet-and-web.png

427 ms

dell.png

dell.png

427 ms

cisco.png

cisco.png

428 ms

oracle.png

oracle.png

437 ms

hp.png

hp.png

470 ms

ibm.png

ibm.png

489 ms

microsoft.png

microsoft.png

539 ms

a9866f2f091f70fc74d996d1cddc235a.jpg

a9866f2f091f70fc74d996d1cddc235a.jpg

539 ms

a9c8d3c0a230d0e72f34d4b7daa07d19_337x215_tc.jpg

a9c8d3c0a230d0e72f34d4b7daa07d19_337x215_tc.jpg

652 ms

c03f0fa3a8dda290c76f5e3842be7028_337x215_tc.jpg

c03f0fa3a8dda290c76f5e3842be7028_337x215_tc.jpg

814 ms

_all.css

_all.css

496 ms

_all.css

_all.css

515 ms

_all.css

_all.css

563 ms

_all.css

_all.css

565 ms

polaris.css

polaris.css

610 ms

futurico.css

futurico.css

628 ms

default

default

140 ms

3f58b41c700bbfede51ff98270f5bbbb.png

3f58b41c700bbfede51ff98270f5bbbb.png

679 ms

24f1ef7538a5e728c6a55c9181c73352_1x455_mc.png

24f1ef7538a5e728c6a55c9181c73352_1x455_mc.png

568 ms

section-news.png

section-news.png

798 ms

sdk.js

sdk.js

13 ms

fa-solid-900.woff

fa-solid-900.woff

227 ms

fa-regular-400.woff

fa-regular-400.woff

233 ms

fa-brands-400.woff

fa-brands-400.woff

233 ms

sdk.js

sdk.js

4 ms

61 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

266 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

67 ms

twk-event-polyfill.js

twk-event-polyfill.js

266 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

120 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

138 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

192 ms

twk-main.js

twk-main.js

80 ms

twk-vendor.js

twk-vendor.js

93 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

108 ms

twk-chunk-common.js

twk-chunk-common.js

125 ms

twk-runtime.js

twk-runtime.js

195 ms

twk-app.js

twk-app.js

141 ms

Accessibility Review

test.bg accessibility score

71

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

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

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

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

test.bg SEO score

85

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

    BG

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

test.bg

Open Graph data is detected on the main page of TEST. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: