6.2 sec in total
595 ms
4 sec
1.6 sec
Click here to check amazing Regent content for Bulgaria. Otherwise, check out these important facts you probably never knew about regent.bg
Намерете своя мечтан имот в Габрово и околностите с РЕГЕНТ Недвижими имоти. Оферти за продажба и наем. Новини, Съвети, Строителство, Кредитиране.
Visit regent.bgWe analyzed Regent.bg page load time and found that the first response time was 595 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
regent.bg performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value12.3 s
0/100
25%
Value8.9 s
15/100
10%
Value2,110 ms
7/100
30%
Value0.001
100/100
15%
Value13.4 s
11/100
10%
595 ms
1195 ms
356 ms
63 ms
24 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 94% of them (80 requests) were addressed to the original Regent.bg, 2% (2 requests) were made to Cdnjs.cloudflare.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Regent.bg.
Page size can be reduced by 76.2 kB (7%)
1.1 MB
1.1 MB
In fact, the total size of Regent.bg main page is 1.1 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. 60% of websites need less resources to load. Images take 953.6 kB which makes up the majority of the site volume.
Potential reduce by 65.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 9.5 kB, which is 12% 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 65.4 kB or 85% of the original size.
Potential reduce by 6.5 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. Regent images are well optimized though.
Potential reduce by 384 B
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.
Potential reduce by 4.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. Regent.bg needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 13% of the original size.
Number of requests can be reduced by 17 (22%)
77
60
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Regent. 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 as a result speed up the page load time.
regent.bg
595 ms
www.regent.bg
1195 ms
main.css
356 ms
js
63 ms
cookieconsent.min.css
24 ms
cookieconsent.min.js
35 ms
jquery-3.1.0.min.js
424 ms
jquery.cookie.js
434 ms
slick.min.js
433 ms
autosize.min.js
424 ms
isInViewport.min.js
433 ms
jquery.form.min.js
433 ms
multiple-select.min.js
553 ms
main.js
545 ms
api.js
44 ms
fbevents.js
181 ms
home.svg
254 ms
heart.svg
249 ms
compare.svg
239 ms
header-logo.svg
244 ms
phone-white.svg
353 ms
hero-home-1.webp
800 ms
hero-home-2.webp
577 ms
arrow-black-down.svg
364 ms
3144392_jpg_22a5504f308570efa1ef464005a8103b.jpg
600 ms
size.svg
366 ms
3184641_jpg_8cc34c771303075084347d5b8d596986.jpg
690 ms
bedroom.svg
484 ms
bathroom.svg
486 ms
3202253_jpg_8d5c489aed72da1541e4f4e9040134a4.jpg
604 ms
2998402_jpg_6b583c7877f3703eb3a8240d16a74343.jpg
605 ms
3201582_jpg_2d6dc7fa4c0c834776db81f82d59a008.jpg
690 ms
3201363_jpg_3ffab4f1ed2208f021a6e8dd16e255ab.jpg
719 ms
3200929_jpg_5749dfaee0ea7f6bb515030e6c1e633a.jpg
723 ms
3199741_jpg_a44600953a50ab4f40eba0c76ba6ae1e.jpg
722 ms
3200020_jpg_c441bfecbc8c9f440de51172b6ecfca7.jpg
802 ms
3199406_jpg_3a8db2942d018b01677cc4bd7377faf3.jpg
803 ms
3198966_jpg_9ab4aa04f1042736e1faae1e6542af32.jpg
838 ms
3143981_jpg_3cb2c237433f8cfacb69f7c9bb519dac.jpg
841 ms
3200140_jpg_a9189790938b63f7e31285f8f82610f0.jpg
841 ms
3199312_jpg_240ff6485023fd9dfed7379e8ceedf61.jpg
910 ms
3197463_jpg_bbda91e83ca45e112f006d05527497f0.jpg
915 ms
2534997_jpg_b3862d29933f4f200a26edee90847317.jpg
915 ms
3149953_jpg_eb69bff193b018ec860244970ae817b6.jpg
840 ms
proximanova-reg-webfont.woff
841 ms
proximanova-bold-webfont.woff
842 ms
proximanova-black-webfont.woff
897 ms
fa-brands-400.woff
1012 ms
fa-solid-900.woff
906 ms
fa-regular-400.woff
945 ms
2964344_jpg_090a97f6ac4655b1658ba71a5a7d28ff.jpg
847 ms
team.svg
843 ms
list-in-bullet.svg
896 ms
chart.svg
903 ms
about-company-bg.webp
1292 ms
about-company-slogan-bg.webp
937 ms
about-accent-1.svg
852 ms
about-accent-3.svg
894 ms
about-accent-2.svg
893 ms
mask-white-2.svg
780 ms
testimonial-bg.webp
834 ms
family1-thumb.png
749 ms
family2-thumb.png
772 ms
family3-thumb.png
769 ms
family4-thumb.png
774 ms
family5-thumb.png
752 ms
family6-thumb.png
754 ms
family7-thumb.png
767 ms
family8-thumb.png
766 ms
family9-thumb.png
769 ms
801_0_png_fcbcd98e69807b6e1bf69af882da2abf.jpg
762 ms
800_0_jpg_700f05defb5334b46f8a39140906ce39.jpg
761 ms
799_0_jpg_7ace3c8a26362e3bb7f5dcc0777b6719.jpg
796 ms
798_0_jpg_8faa338e27ae8ae8a4b7a766ff391cf2.jpg
762 ms
bacb-logo-color-bg.svg
765 ms
partners-2.png
832 ms
lilly-logo.svg
768 ms
radev-logo.svg
767 ms
detelina-logo.png
797 ms
ceratizit-logo.svg
756 ms
unitrade-logo.png
749 ms
footer-background.svg
807 ms
paperplane.svg
762 ms
footer-logo.svg
736 ms
envelope-white.svg
744 ms
regent.bg accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
regent.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
regent.bg SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Regent.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 Regent.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.
regent.bg
Open Graph data is detected on the main page of Regent. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: