8.8 sec in total
568 ms
7 sec
1.3 sec
Click here to check amazing Regent content for Bulgaria. Otherwise, check out these important facts you probably never knew about regent.bg
imoti,imot,имоти,недвижими имоти,продажба имот,агенция,регент,nedvigimi imoti,nedvijimi imoti,недвижим имот,недвижими,имоти,кантора имоти,брокери имоти,agencia imoti,Габровски имоти,imoti,продажба,про...
Visit regent.bgWe analyzed Regent.bg page load time and found that the first response time was 568 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
regent.bg performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value20.0 s
0/100
25%
Value26.2 s
0/100
10%
Value31,910 ms
0/100
30%
Value0.004
100/100
15%
Value43.3 s
0/100
10%
568 ms
973 ms
463 ms
73 ms
58 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 91% of them (72 requests) were addressed to the original Regent.bg, 3% (2 requests) were made to Cdnjs.cloudflare.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Regent.bg.
Page size can be reduced by 77.2 kB (7%)
1.1 MB
978.4 kB
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. 40% of websites need less resources to load. Images take 876.7 kB which makes up the majority of the site volume.
Potential reduce by 65.7 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.1 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.7 kB or 84% of the original size.
Potential reduce by 7.1 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 442 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 18 (25%)
71
53
The browser has sent 71 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 13 to 1 for JavaScripts and as a result speed up the page load time.
regent.bg
568 ms
www.regent.bg
973 ms
main.css
463 ms
js
73 ms
cookieconsent.min.css
58 ms
cookieconsent.min.js
66 ms
jquery-3.1.0.min.js
620 ms
jquery.cookie.js
350 ms
slick.min.js
358 ms
autosize.min.js
359 ms
isInViewport.min.js
365 ms
jquery.form.min.js
777 ms
multiple-select.min.js
885 ms
main.js
783 ms
api.js
77 ms
fbevents.js
167 ms
home.svg
268 ms
heart.svg
395 ms
compare.svg
397 ms
header-logo.svg
607 ms
phone-white.svg
610 ms
hero-home-1.webp
1213 ms
hero-home-2.webp
1048 ms
arrow-black-down.svg
728 ms
2544641_jpg_b6edcaf7101a2763352f0892d38178bd.jpg
857 ms
bedroom.svg
946 ms
bathroom.svg
967 ms
size.svg
1067 ms
2680105_jpg_941490e8fdb176872711937383203c14.jpg
1332 ms
2675979_jpg_7adc8b7ba2891c5a784aa7c75a51e1a7.jpg
1397 ms
noimage_png_9cb800d9e2de4cbfb9d84f52a7a0ce30.png
1640 ms
2647225_jpg_9bd7a29a58af8d6022a2145227c6e485.jpg
1630 ms
2676265_jpg_c45bdf2d90bb9b74fad98d6164a96f5b.jpg
1649 ms
2535580_jpg_7977908ab1b93c5ebe0982ae9a8c844e.jpg
1679 ms
2675697_jpg_bfd8b03fae96933becf96c9153daaaff.jpg
1894 ms
2676488_jpg_dcf40a47bc3bf1f6425dd6cafc849305.jpg
1868 ms
2673897_jpg_e27849381bec142d6c0c5b1a514b28a6.jpg
2080 ms
2673497_jpg_d4f6d3a2a2aa158198cdfe0c09dcc07b.jpg
2223 ms
2657544_jpg_2cb3cc52e7f597d0f3e2aee5019744f3.jpg
2237 ms
2033859_jpg_1d6214d4a2ccf664bc847bd549c716ae.jpg
2132 ms
101319_jpg_ad5c762ec8df32ec5f03d6c485ed3637.jpg
2341 ms
2453478_jpg_93c940a21893debe61288085d980029f.jpg
2347 ms
2675813_jpg_7e3ce38970e7eb43f4107debf2b11299.jpg
2533 ms
128422_jpg_8d31d7b92708ac542f6e0aa1f80dc504.jpg
2721 ms
2675717_jpg_513fd53cea8d6f59aeeb754acc3fe233.jpg
2789 ms
team.svg
2580 ms
list-in-bullet.svg
2682 ms
chart.svg
2600 ms
analytics.js
36 ms
proximanova-reg-webfont.woff
2864 ms
collect
13 ms
proximanova-bold-webfont.woff
2791 ms
proximanova-black-webfont.woff
2887 ms
fa-brands-400.woff
3024 ms
fa-solid-900.woff
3014 ms
fa-regular-400.woff
2865 ms
about-company-bg.webp
3499 ms
about-company-slogan-bg.webp
2898 ms
about-accent-1.svg
2898 ms
about-accent-3.svg
2875 ms
about-accent-2.svg
2788 ms
mask-white-2.svg
2796 ms
testimonial-bg.webp
3099 ms
family-thumb.jpg
2811 ms
753_0_jpg_51a4e78d4c39ed9ab80f492bb678d0c0.jpg
2988 ms
752_0_png_ac2ffd1ff4435ed76e50d2cf146e9645.jpg
2899 ms
751_0_jpg_608cce57c8373618704eef9908c8c9d6.jpg
2879 ms
750_0_jpg_0e6412760840a2b5719ab8c3d9570ce5.jpg
2816 ms
bacb-logo-color-bg.svg
2609 ms
partners-2.png
2773 ms
lilly-logo.svg
2760 ms
radev-logo.svg
2770 ms
detelina-logo.png
2681 ms
ceratizit-logo.svg
2669 ms
unitrade-logo.png
2510 ms
footer-background.svg
2617 ms
paperplane.svg
2540 ms
footer-logo.svg
2552 ms
envelope-white.svg
2547 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: