Tools & Wizards About Us
infonotary.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

infonotary.com

InfoNotary

Page Load Speed

9.4 sec in total

First Response

376 ms

Resources Loaded

8.8 sec

Page Rendered

254 ms

infonotary.com screenshot

About Website

Visit infonotary.com now to see the best up-to-date Info Notary content for Bulgaria and also check out these interesting facts you probably never knew about infonotary.com

публични услуги по издаване и управление на Удостоверения за квалифициран електронен подпис, електронен подпис, цифров подпис, публични удостоверителни услуги, удостоверения за електронен подпис, елек...

Visit infonotary.com

Key Findings

We analyzed Infonotary.com page load time and found that the first response time was 376 ms and then it took 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

infonotary.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.404

25/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

infonotary.com

376 ms

6317 ms

_style.css

339 ms

bootstrap.bundle.min.js

615 ms

css2

32 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 97% of them (67 requests) were addressed to the original Infonotary.com, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Infonotary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (63%)

Content Size

2.0 MB

After Optimization

731.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Infonotary.com main page is 2.0 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. 25% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 17.6 kB

  • Original 21.1 kB
  • After minification 14.1 kB
  • After compression 3.4 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 6.9 kB, which is 33% 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 17.6 kB or 84% of the original size.

Image Optimization

-60%

Potential reduce by 1.0 MB

  • Original 1.7 MB
  • After minification 684.2 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, Info Notary needs image optimization as it can save up to 1.0 MB or 60% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 61.9 kB

  • Original 87.1 kB
  • After minification 85.0 kB
  • After compression 25.2 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 61.9 kB or 71% of the original size.

CSS Optimization

-89%

Potential reduce by 153.5 kB

  • Original 171.9 kB
  • After minification 106.0 kB
  • After compression 18.5 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. Infonotary.com needs all CSS files to be minified and compressed as it can save up to 153.5 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (48%)

Requests Now

63

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

infonotary.com

infonotary.com

376 ms

6317 ms

_style.css

_style.css

339 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

615 ms

css2

css2

32 ms

general.css

general.css

113 ms

grid.css

grid.css

226 ms

header.css

header.css

449 ms

animations.css

animations.css

586 ms

carousel.css

carousel.css

354 ms

accordion.css

accordion.css

355 ms

home-page.css

home-page.css

398 ms

footer.css

footer.css

472 ms

_inner-page-banners.css

_inner-page-banners.css

473 ms

_common-elements.css

_common-elements.css

520 ms

page-personal-and-corporate-sign-and-seal.css

page-personal-and-corporate-sign-and-seal.css

562 ms

page_psd-certificate.css

page_psd-certificate.css

588 ms

page_ssl.css

page_ssl.css

591 ms

page_advanced-signature.css

page_advanced-signature.css

643 ms

page_timestamp.css

page_timestamp.css

674 ms

page_validation.css

page_validation.css

702 ms

page_business-development.css

page_business-development.css

705 ms

page_business-development-new.css

page_business-development-new.css

709 ms

page_consulting-services.css

page_consulting-services.css

765 ms

page_inss_and_one-time-signature.css

page_inss_and_one-time-signature.css

786 ms

page_hsm.css

page_hsm.css

819 ms

page_documents.css

page_documents.css

823 ms

page_technical-support.css

page_technical-support.css

827 ms

page_contacts-and-offices.css

page_contacts-and-offices.css

886 ms

page_about-us.css

page_about-us.css

898 ms

page_404.css

page_404.css

935 ms

logo-in.svg

logo-in.svg

114 ms

search-1.svg

search-1.svg

123 ms

aside_menage.svg

aside_menage.svg

122 ms

aside_contacts.svg

aside_contacts.svg

118 ms

aside_support.svg

aside_support.svg

119 ms

aside_offices.svg

aside_offices.svg

225 ms

font

font

18 ms

NunitoSans-Regular.ttf

NunitoSans-Regular.ttf

218 ms

NunitoSans-Light.ttf

NunitoSans-Light.ttf

219 ms

NunitoSans-Bold.ttf

NunitoSans-Bold.ttf

220 ms

www.infonotary.com

www.infonotary.com

1076 ms

www.infonotary.com

www.infonotary.com

1093 ms

www.infonotary.com

www.infonotary.com

1040 ms

home-carousel_locations_xs-query-320px.png

home-carousel_locations_xs-query-320px.png

675 ms

home-carousel_validation_xs-query-320px.png

home-carousel_validation_xs-query-320px.png

859 ms

home-carousel_business_xs-query-320px.png

home-carousel_business_xs-query-320px.png

709 ms

arrow-left.svg

arrow-left.svg

118 ms

arrow-right.svg

arrow-right.svg

119 ms

icon-section-1.svg

icon-section-1.svg

235 ms

icon-1-1.svg

icon-1-1.svg

237 ms

icon-1-2.svg

icon-1-2.svg

352 ms

icon-1-4.svg

icon-1-4.svg

354 ms

icon-1-5.svg

icon-1-5.svg

468 ms

icon-1-6.svg

icon-1-6.svg

471 ms

icon-section-2.svg

icon-section-2.svg

753 ms

icon-2-1.svg

icon-2-1.svg

586 ms

icon-2-2.svg

icon-2-2.svg

589 ms

icon-section-3.svg

icon-section-3.svg

704 ms

icon-3-1.svg

icon-3-1.svg

706 ms

icon-3-2.svg

icon-3-2.svg

786 ms

icon-3-3.svg

icon-3-3.svg

820 ms

icon-3-4.svg

icon-3-4.svg

824 ms

icon-3-5.svg

icon-3-5.svg

826 ms

header.js

header.js

475 ms

hashRouter.js

hashRouter.js

502 ms

TUV-Certified.png

TUV-Certified.png

2059 ms

eu.png

eu.png

542 ms

animations.js

animations.js

544 ms

Accessibility Review

infonotary.com accessibility score

85

Accessibility Issues

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

Links do not have a discernible name

Best Practices

infonotary.com 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

infonotary.com SEO score

92

Search Engine Optimization Advices

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 Infonotary.com 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 Infonotary.com 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

infonotary.com

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