5.1 sec in total
634 ms
4.3 sec
213 ms
Visit megapark.bg now to see the best up-to-date MEGAPARK content and also check out these interesting facts you probably never knew about megapark.bg
Офиси Клас А и търговски площи под наем в Бизнес център Мегапарк на бул. Цариградско шосе в град София в сграда с максимален комфорт и забележителен дизайн
Visit megapark.bgWe analyzed Megapark.bg page load time and found that the first response time was 634 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
megapark.bg performance score
name
value
score
weighting
Value12.2 s
0/100
10%
Value12.8 s
0/100
25%
Value16.6 s
0/100
10%
Value260 ms
83/100
30%
Value0.237
53/100
15%
Value15.6 s
6/100
10%
634 ms
262 ms
402 ms
684 ms
516 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 97% of them (72 requests) were addressed to the original Megapark.bg, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Megapark.bg.
Page size can be reduced by 43.2 kB (62%)
69.3 kB
26.1 kB
In fact, the total size of Megapark.bg main page is 69.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. HTML takes 43.0 kB which makes up the majority of the site volume.
Potential reduce by 35.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. 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 35.4 kB or 82% of the original size.
Potential reduce by 34 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 7.7 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. Megapark.bg needs all CSS files to be minified and compressed as it can save up to 7.7 kB or 85% of the original size.
Number of requests can be reduced by 12 (17%)
70
58
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MEGAPARK. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
megapark.bg
634 ms
_default.css
262 ms
stmenu.js
402 ms
jquery.js
684 ms
naemateli-megapark.png
516 ms
background.gif
252 ms
body-background.gif
262 ms
shadow-left.gif
271 ms
shadow-top-left.gif
276 ms
header-background.gif
405 ms
spacer.gif
501 ms
background.gif
530 ms
flag-eng.gif
542 ms
separator.gif
550 ms
gallery.gif
812 ms
pano.gif
772 ms
floor-plans.gif
793 ms
shadow-top-right.gif
811 ms
stdom.js
665 ms
stinit.js
681 ms
blank.gif
872 ms
background.gif
914 ms
background-active.gif
920 ms
menu-bullet.gif
919 ms
sthilight.js
258 ms
pointer-background.gif
286 ms
panel-background.gif
437 ms
collage-02.jpg
997 ms
collage-03.jpg
1039 ms
collage-01.jpg
755 ms
collage-05.jpg
873 ms
vertical-separator.gif
554 ms
shadow-right.gif
675 ms
footer-background.gif
823 ms
ga.js
8 ms
__utm.gif
12 ms
logo-1.png
695 ms
logo-2.png
734 ms
logo-3.png
844 ms
logo-4.png
853 ms
logo-5.png
944 ms
logo-6.png
982 ms
logo-7.png
994 ms
logo-8.png
1025 ms
logo-9.png
1091 ms
logo-10.png
1128 ms
logo-11.png
1210 ms
logo-12.png
1254 ms
logo-13.png
1252 ms
logo-14.png
1301 ms
logo-15.png
1339 ms
logo-16.png
1401 ms
logo-17.png
1476 ms
logo-18.png
1519 ms
logo-19.png
1529 ms
logo-20.png
1584 ms
logo-21.png
1626 ms
logo-22.png
1673 ms
logo-23.png
1733 ms
logo-24.png
1767 ms
logo-25.png
1786 ms
logo-26.png
1855 ms
logo-27.png
1894 ms
logo-28.png
1938 ms
logo-29.png
1836 ms
logo-30.png
1749 ms
logo-31.png
1656 ms
logo-32.png
1648 ms
logo-33.png
1602 ms
logo-34.png
1617 ms
logo-35.png
1579 ms
logo-36.png
1681 ms
logo-37.png
1620 ms
logo-38.png
1634 ms
megapark.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
Links do not have a discernible name
megapark.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
megapark.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
EN
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Megapark.bg can be misinterpreted by Google and other search engines. Our service has detected that English 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 Megapark.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.
megapark.bg
Open Graph description is not detected on the main page of MEGAPARK. 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: