5.1 sec in total
464 ms
4.5 sec
177 ms
Click here to check amazing A 1 content for Bulgaria. Otherwise, check out these important facts you probably never knew about a1.bg
A1.BG - цялостни телекомуникационни решения – мобилни и фиксирани услуги, най-новите модели смартфони и устройства. Дигитални, бизнес и финансови услуги. Купи бързо и лесно онлайн.
Visit a1.bgWe analyzed A1.bg page load time and found that the first response time was 464 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
a1.bg performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value12.6 s
0/100
25%
Value11.8 s
4/100
10%
Value290 ms
80/100
30%
Value0.573
12/100
15%
Value22.2 s
1/100
10%
464 ms
224 ms
700 ms
337 ms
60 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 59% of them (45 requests) were addressed to the original A1.bg, 28% (21 requests) were made to Media.a1.bg and 5% (4 requests) were made to Ads.a1.bg. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Media.a1.bg.
Page size can be reduced by 782.7 kB (60%)
1.3 MB
511.7 kB
In fact, the total size of A1.bg main page is 1.3 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. 40% of websites need less resources to load. Images take 422.3 kB which makes up the majority of the site volume.
Potential reduce by 153.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 153.3 kB or 81% of the original size.
Potential reduce by 376.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, A 1 needs image optimization as it can save up to 376.2 kB or 89% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 142.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 142.2 kB or 34% of the original size.
Potential reduce by 111.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. A1.bg needs all CSS files to be minified and compressed as it can save up to 111.0 kB or 42% of the original size.
Number of requests can be reduced by 38 (53%)
72
34
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A 1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
bg
464 ms
basic.css
224 ms
b73f2e2b3a4c47d2bc8a754a7639a45c.js
700 ms
modernizr.custom.41931.js
337 ms
OtAutoBlock.js
60 ms
otSDKStub.js
78 ms
socket.io.min.js
46 ms
require.js
231 ms
teneo-web-chat-v3.7.10.js
899 ms
TWCExtensionBase.js
330 ms
teneo-ef-extension.js
481 ms
42a1fcf8-5dbb-4afb-bebf-2c8bf1e69f67.json
39 ms
A1-logo.jpg
113 ms
empty-2-1.gif
673 ms
Basic-menu-60x60-01.png
140 ms
Basic-menu-60x60-10.png
145 ms
roaming-01-01.png
148 ms
Basic-menu-60x60-15.png
152 ms
Basic-menu-60x60-08.png
244 ms
01.png
289 ms
02.png
284 ms
03.png
292 ms
04.png
291 ms
xplore-tv-icon.png
387 ms
01.png
411 ms
05.png
434 ms
05.png
442 ms
06.png
443 ms
Basic-menu-60x60-15.png
432 ms
Basic-menu-60x60-08.png
525 ms
A1_Wallet_icon_new.png
555 ms
ConsumerLoan_icon_new.png
620 ms
Credit_card_icon_new.png
599 ms
Insurance_icon_new.png
607 ms
08.png
591 ms
04.png
673 ms
10.png
712 ms
09.png
742 ms
16.png
749 ms
VIP_client_black_60x40px.png
777 ms
Iphone-preorder-carousel_160x75.png
687 ms
carousel_160x75.png
691 ms
carousel_160x75.jpg
702 ms
carousel_160x75.png
820 ms
carousel_160x75_v2.png
708 ms
carousel_160x75.png
776 ms
location
37 ms
Mobile-v3.svg
782 ms
paket-televizia-internet-80px.svg
784 ms
mobile.svg
796 ms
Icon_MyA1-01.svg
805 ms
mobilen-internet-80px.svg
867 ms
Vinetka-01.svg
891 ms
Credit_card.svg
895 ms
wallet.svg
908 ms
Tennis.svg
916 ms
Mtel-katalog-80px.svg
918 ms
MBB-pro-max-700x450.png
1648 ms
Audio-700x450.png
1491 ms
ajs.php
614 ms
lg.php
351 ms
ajs.php
353 ms
7f8ddf6df4c6540f7187600a4caa135e.css
346 ms
lg.php
485 ms
generic.css
116 ms
ui.svg
199 ms
A1-logo-small.jpg
197 ms
ui.svg
295 ms
instagram-28px.png
196 ms
A1SansV5-Regular.otf
337 ms
A1SansV5-Light.otf
448 ms
A1SansV5-Bold.otf
540 ms
A1SerifV51-Regular.ttf
562 ms
A1Serif-Light.ttf
561 ms
A1SerifV51-Bold.ttf
336 ms
print.css
118 ms
a1.bg accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
a1.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
a1.bg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
BG
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A1.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 A1.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.
a1.bg
Open Graph description is not detected on the main page of A 1. 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: