4.6 sec in total
622 ms
3.6 sec
408 ms
Welcome to megaplants.bg homepage info - get ready to check Megaplants best content right away, or after learning these important things about megaplants.bg
Градински цветя онлайн и растения с намаление от 50% до 90%
Visit megaplants.bgWe analyzed Megaplants.bg page load time and found that the first response time was 622 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
megaplants.bg performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value5.2 s
23/100
25%
Value7.1 s
31/100
10%
Value1,040 ms
25/100
30%
Value0.046
99/100
15%
Value10.1 s
26/100
10%
622 ms
376 ms
53 ms
504 ms
34 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 69% of them (52 requests) were addressed to the original Megaplants.bg, 8% (6 requests) were made to Googletagmanager.com and 5% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Megaplants.bg.
Page size can be reduced by 230.2 kB (13%)
1.8 MB
1.6 MB
In fact, the total size of Megaplants.bg main page is 1.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 184.8 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 119.4 kB, which is 60% 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 184.8 kB or 93% of the original size.
Potential reduce by 32.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. Megaplants images are well optimized though.
Potential reduce by 8.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 5.2 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. Megaplants.bg needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 11% of the original size.
Number of requests can be reduced by 34 (49%)
69
35
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Megaplants. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
megaplants.bg
622 ms
9666d17c53.js
376 ms
jquery-latest.js
53 ms
reset.css
504 ms
scripts.css
34 ms
custom.css
503 ms
animate.css
34 ms
jquery.bxslider.css
511 ms
bootstrap.css
34 ms
bootstrap.js
46 ms
jquery.carousel.js
520 ms
words.js
516 ms
jquery.reveal.js
54 ms
scripts.js
449 ms
jquery-ui.js
459 ms
purchase_popup.js
469 ms
toogle.js
475 ms
smoothscroll.js
483 ms
jquery.tipsy.js
491 ms
all.js
44 ms
bjqs-1.3.min.js
499 ms
email-decode.min.js
500 ms
js
87 ms
9666d17c53.css
241 ms
font-awesome-css.min.css
42 ms
car.svg
1095 ms
poof.svg
1094 ms
sign.svg
1093 ms
logo.png
1096 ms
064069bf309f445e7b29f2365cb2ea9f_small.jpg
1098 ms
351fd747b7cc6b3d42469a71542e8dc3_small.jpg
1100 ms
a05f68a85141289019a570ed18e3f9f5_small.jpg
1671 ms
14c8bf3844ffec043fdc31430001d879_small.jpg
1668 ms
18892c683b5fe09f82de088ceee25d11_small.jpg
1166 ms
c53226166f69b389580aa1449f3cfc6f_small.png
1859 ms
bd2a482b73f76f494a548965cd2c5362_small.png
1885 ms
b773f82034a4a30413e23cea86c39772_small.jpg
1166 ms
ab2ea04a02811bce7a5336d5a9e9f449_small.jpeg
1172 ms
de38b9addb244f93b61a951cce5ce622_small.jpg
1602 ms
17134965559b592613965e59909a7a3b_small.jpg
1176 ms
ff6f8e43ae17f3d3a67cd0f70183bac1_small.jpg
1185 ms
3e106c8b47b13445ce40987c136f6657_small.jpg
1193 ms
ca8a7398a0f938596d6d0c6888d4a0f9_small.jpg
1202 ms
b7af0e3ffee2c03e598f1362502a89c8_small.jpg
1210 ms
6b4d002ea1932e2cd622a72c2332ec2d_small.jpg
1223 ms
282492eb830f6a3bfbce379b7282433f_small.jpg
1231 ms
5b2e7bc63a890948f6f20e9430d51147_small.jpg
1240 ms
9f06a5339362e80cdccd85bbf9b53c7e_small.jpg
1252 ms
91bbd0aa565632104be7119c8e0d455d_small.jpg
1260 ms
5cfef053f04af0766bda291ffc625c36_small.jpg
1266 ms
06c552029b6ca6fc0caec5bd242b2123_small.jpg
1273 ms
37ab9137194db156a218d5325b1011ad_small.jpg
1281 ms
3c2d4a6af1ddb1756b17177c9b47108d_small.jpg
1290 ms
ekont_express.jpg
1298 ms
gtm.js
61 ms
all.js
10 ms
lupa.png
1771 ms
arrow_c_t.png
2031 ms
OpenSans-Regular.ttf
2088 ms
fontawesome-webfont.woff
107 ms
new.png
2069 ms
js
108 ms
fbevents.js
23 ms
pixel.js
94 ms
js
54 ms
page.php
201 ms
fingerprint2.min.js
161 ms
destination
164 ms
js
666 ms
analytics.js
661 ms
yQ9dBGkIifz.css
645 ms
648 ms
client.js
267 ms
collect
23 ms
36 ms
megaplants.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.
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
Image elements do not have [alt] attributes
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.
megaplants.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
Browser errors were logged to the console
megaplants.bg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Megaplants.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 Megaplants.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.
megaplants.bg
Open Graph description is not detected on the main page of Megaplants. 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: