4.9 sec in total
694 ms
4 sec
227 ms
Click here to check amazing Sirma content for Bulgaria. Otherwise, check out these important facts you probably never knew about sirma.bg
Navigate organizations' intelligent evolution by mastering Data, Information & Knowledge. Evolve our technologies towards better knowledge management & AI.
Visit sirma.bgWe analyzed Sirma.bg page load time and found that the first response time was 694 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
sirma.bg performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value3.8 s
55/100
25%
Value2.9 s
95/100
10%
Value760 ms
39/100
30%
Value0
100/100
15%
Value8.4 s
39/100
10%
694 ms
1096 ms
173 ms
234 ms
238 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sirma.bg, 84% (67 requests) were made to Sirma.com and 9% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Sirma.com.
Page size can be reduced by 294.4 kB (35%)
852.3 kB
557.9 kB
In fact, the total size of Sirma.bg main page is 852.3 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. 40% of websites need less resources to load. Images take 598.5 kB which makes up the majority of the site volume.
Potential reduce by 22.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 22.9 kB or 79% of the original size.
Potential reduce by 114.6 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, Sirma needs image optimization as it can save up to 114.6 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 133.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 133.4 kB or 68% of the original size.
Potential reduce by 23.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. Sirma.bg needs all CSS files to be minified and compressed as it can save up to 23.5 kB or 83% of the original size.
Number of requests can be reduced by 14 (20%)
71
57
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sirma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
sirma.bg
694 ms
1096 ms
style.css
173 ms
carousel.css
234 ms
chronologystile.css
238 ms
jquery-1.7.2.min.js
365 ms
jquery.infinitecarousel3.js
244 ms
easing.js
342 ms
sirma.js
349 ms
fadeSlideShow.js
346 ms
chronology.js
353 ms
lang.js
381 ms
js
50 ms
css
34 ms
css
49 ms
editor-style-shared.css
508 ms
page-list.css
460 ms
analytics.js
70 ms
logo-sgh-header.png
172 ms
logo-facebook.png
119 ms
logo-linkedin.png
120 ms
shadow-up.png
121 ms
banner-1-cloudservice2.jpg
521 ms
banner-1-packaging2.jpg
242 ms
banner-2-innovationcenter2.jpg
233 ms
banner-2-banking3.jpg
356 ms
banner-2-insurance2.jpg
240 ms
banner-3-eqma2.jpg
506 ms
banner-4-ontotext2.jpg
466 ms
banner-4-systemintegration2.jpg
359 ms
banner-5-bipper2.jpg
482 ms
banner-5-masterpublishing2.jpg
711 ms
banner-6-loyax2.jpg
480 ms
banner-6-mobilewallet2.jpg
697 ms
shadow.png
599 ms
h1-bcgr-gray.png
601 ms
logo-companies-sgh1.png
674 ms
index-work-image.jpg
1040 ms
custom-ul-bullet.png
717 ms
logo-bottom-ssolutions-gray1.png
720 ms
logo-bottom-ssolutions1.png
1013 ms
logo-bottom-ontotext-gray1.png
811 ms
logo-bottom-ontotext1.png
827 ms
logo-bottom-engview-gray.png
835 ms
logo-bottom-engview.png
838 ms
logo-bottom-smedia-gray1.png
927 ms
logo-bottom-smedia2.png
946 ms
logo-bottom-sbc-gray.png
953 ms
logo-bottom-sbc1.png
959 ms
logo-bottom-daticum-gray2.png
1043 ms
logo-bottom-daticum2.png
1064 ms
logo-bottom-smobile-gray1.png
1071 ms
logo-bottom-smobile1.png
1078 ms
logo-bottom-sisg-gray.png
1129 ms
c2KTkZ_oLp2UOMwi4GGs9A.woff
16 ms
IiMFELcoPB-OzGzq14k4ej8E0i7KZn-EPnyo3HZu7kw.woff
17 ms
nBF2d6Y3AbOwfkBM-9HcWD8E0i7KZn-EPnyo3HZu7kw.woff
16 ms
4z2U46_RRLOfkoHsWJG3vz8E0i7KZn-EPnyo3HZu7kw.woff
16 ms
Fl4y0QdOxyyTHEGMXX8kcT8E0i7KZn-EPnyo3HZu7kw.woff
15 ms
Y5yuUJGDLtmYv2_3fMB4fA.woff
15 ms
isZ-wbCXNKAbnjo6_TwHTj8E0i7KZn-EPnyo3HZu7kw.woff
16 ms
collect
25 ms
logo-bottom-sisg1.png
1102 ms
logo-bottom-panaton-gray.png
1048 ms
logo-bottom-panaton.png
1069 ms
logo-bottom-sitt-gray.png
1028 ms
logo-bottom-sitt.png
972 ms
googlemap.png
1044 ms
bg_box.png
1117 ms
logo-bottom-ssolutions.png
170 ms
logo-bottom-ontotext.png
118 ms
logo-bottom-engview.png
121 ms
logo-bottom-smedia.png
120 ms
logo-bottom-sbc.png
175 ms
logo-bottom-sitt.png
122 ms
logo-bottom-daticum.png
233 ms
logo-bottom-pirina.png
239 ms
logo-bottom-smobile.png
238 ms
logo-bottom-sisg.png
240 ms
logo-bottom-panaton.png
337 ms
sirma.bg accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sirma.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
sirma.bg SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
BG
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sirma.bg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Bulgarian language. Our system also found out that Sirma.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.
sirma.bg
Open Graph description is not detected on the main page of Sirma. 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: