9.5 sec in total
1.4 sec
7.8 sec
270 ms
Click here to check amazing Buzz Mar content for Turkey. Otherwise, check out these important facts you probably never knew about buzzmar.com
My Buzz Mar | Online Alışverişte Yeni ÇizgiStore
Visit buzzmar.comWe analyzed Buzzmar.com page load time and found that the first response time was 1.4 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
buzzmar.com performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value13.1 s
0/100
25%
Value10.9 s
6/100
10%
Value2,320 ms
5/100
30%
Value0.196
63/100
15%
Value10.4 s
24/100
10%
1415 ms
275 ms
984 ms
422 ms
582 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 96% of them (136 requests) were addressed to the original Buzzmar.com, 1% (2 requests) were made to Proticaret.org and 1% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Buzzmar.com.
Page size can be reduced by 857.7 kB (60%)
1.4 MB
574.0 kB
In fact, the total size of Buzzmar.com main page is 1.4 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. 70% of websites need less resources to load. Javascripts take 633.0 kB which makes up the majority of the site volume.
Potential reduce by 109.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 109.3 kB or 85% of the original size.
Potential reduce by 37.7 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. Buzz Mar images are well optimized though.
Potential reduce by 457.9 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 457.9 kB or 72% of the original size.
Potential reduce by 252.8 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. Buzzmar.com needs all CSS files to be minified and compressed as it can save up to 252.8 kB or 89% of the original size.
Number of requests can be reduced by 24 (17%)
138
114
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buzz Mar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
buzzmar.com
1415 ms
reset.css
275 ms
Portal.css
984 ms
popup-modal.css
422 ms
WebResource.axd
582 ms
ScriptResource.axd
596 ms
ScriptResource.axd
544 ms
ScriptResource.axd
564 ms
js
693 ms
js
711 ms
js
727 ms
js
754 ms
js
755 ms
js
831 ms
jquery.min.js
1270 ms
jquery-ui.min.js
1310 ms
ui.selectmenu.min.js
898 ms
jquery-colorbox.min.js
901 ms
global.js
966 ms
jquery.cookie.min.js
917 ms
fontello.css
1208 ms
animation.css
983 ms
tr.png
1064 ms
us.png
1101 ms
logo.png
1127 ms
loading.gif
1243 ms
makethumb.aspx
1263 ms
makethumb.aspx
1795 ms
makethumb.aspx
1285 ms
makethumb.aspx
1333 ms
makethumb.aspx
1888 ms
makethumb.aspx
1362 ms
makethumb.aspx
1411 ms
makethumb.aspx
1441 ms
makethumb.aspx
1355 ms
makethumb.aspx
1381 ms
makethumb.aspx
1420 ms
makethumb.aspx
1318 ms
owl.carousel.js
1248 ms
makethumb.aspx
1269 ms
conversion.js
20 ms
attrchange.js
602 ms
copyright.js
600 ms
rendermodules.js
1262 ms
makethumb.aspx
1326 ms
makethumb.aspx
1358 ms
makethumb.aspx
1296 ms
makethumb.aspx
1790 ms
makethumb.aspx
1339 ms
makethumb.aspx
1339 ms
makethumb.aspx
1360 ms
makethumb.aspx
1312 ms
makethumb.aspx
1293 ms
makethumb.aspx
1315 ms
makethumb.aspx
1236 ms
makethumb.aspx
1227 ms
makethumb.aspx
1201 ms
makethumb.aspx
1233 ms
makethumb.aspx
1172 ms
makethumb.aspx
1159 ms
makethumb.aspx
1176 ms
makethumb.aspx
1168 ms
makethumb.aspx
1692 ms
GetShoppingCartCount
1149 ms
GetShoppingCartTotal
1173 ms
fontello.woff
1485 ms
makethumb.aspx
1193 ms
makethumb.aspx
1177 ms
makethumb.aspx
1188 ms
makethumb.aspx
1170 ms
makethumb.aspx
1200 ms
makethumb.aspx
1162 ms
makethumb.aspx
1186 ms
makethumb.aspx
1184 ms
makethumb.aspx
1210 ms
makethumb.aspx
1154 ms
makethumb.aspx
1173 ms
68 ms
makethumb.aspx
1184 ms
categoryserviceall.aspx
1645 ms
34 ms
brandservice.aspx
1176 ms
ShoppingCartImages.aspx
1684 ms
ajaxsearch.aspx
1185 ms
makethumb.aspx
1655 ms
makethumb.aspx
1121 ms
makethumb.aspx
1178 ms
makethumb.aspx
1212 ms
makethumb.aspx
1197 ms
makethumb.aspx
1231 ms
makethumb.aspx
1266 ms
makethumb.aspx
1251 ms
makethumb.aspx
1302 ms
makethumb.aspx
2343 ms
makethumb.aspx
1792 ms
banner.png
1324 ms
slider1.png
1621 ms
slider2.png
1465 ms
slider3.png
1373 ms
slider4.png
1347 ms
slider5.png
1446 ms
slider6.png
1437 ms
slider7.png
1421 ms
slider8.png
1476 ms
banner2.png
1451 ms
makethumb.aspx
1454 ms
makethumb.aspx
1399 ms
makethumb.aspx
1482 ms
makethumb.aspx
1452 ms
makethumb.aspx
2421 ms
makethumb.aspx
1425 ms
makethumb.aspx
1893 ms
makethumb.aspx
1490 ms
makethumb.aspx
1458 ms
makethumb.aspx
1478 ms
makethumb.aspx
1559 ms
makethumb.aspx
1514 ms
makethumb.aspx
2517 ms
makethumb.aspx
1569 ms
makethumb.aspx
1512 ms
makethumb.aspx
1469 ms
makethumb.aspx
1587 ms
makethumb.aspx
1524 ms
makethumb.aspx
3499 ms
makethumb.aspx
1496 ms
makethumb.aspx
1552 ms
makethumb.aspx
2556 ms
makethumb.aspx
1653 ms
makethumb.aspx
1594 ms
makethumb.aspx
1752 ms
makethumb.aspx
2637 ms
makethumb.aspx
2119 ms
makethumb.aspx
1713 ms
homelabel-indirim-icon.png
1789 ms
homelabel-ucretsiz-icon.png
1845 ms
home-label-firsat-icon.png
1895 ms
overlay.png
1944 ms
controls.png
1935 ms
border.png
1963 ms
loading_background.png
1984 ms
loading.gif
2032 ms
buzzmar.com 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
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.
buzzmar.com 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
buzzmar.com 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
TR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buzzmar.com can be misinterpreted by Google and other search engines. Our service has detected that Turkish 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 Buzzmar.com 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.
buzzmar.com
Open Graph description is not detected on the main page of Buzz Mar. 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: