10.7 sec in total
681 ms
9.2 sec
834 ms
Visit markobrando.com now to see the best up-to-date Marko Brando content and also check out these interesting facts you probably never knew about markobrando.com
From strategy to execution, Marko & Brando is your partner in digital transformation. Experience marketing that's not just effective but also memorable. Join us.
Visit markobrando.comWe analyzed Markobrando.com page load time and found that the first response time was 681 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
markobrando.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value6.5 s
9/100
25%
Value8.3 s
19/100
10%
Value620 ms
48/100
30%
Value0.034
100/100
15%
Value10.3 s
24/100
10%
681 ms
874 ms
155 ms
653 ms
53 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 71% of them (60 requests) were addressed to the original Markobrando.com, 8% (7 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Markobrando.com.
Page size can be reduced by 38.1 kB (15%)
252.4 kB
214.3 kB
In fact, the total size of Markobrando.com main page is 252.4 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. 60% of websites need less resources to load. Images take 170.8 kB which makes up the majority of the site volume.
Potential reduce by 38.0 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 38.0 kB or 77% of the original size.
Potential reduce by 40 B
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. Marko Brando images are well optimized though.
Potential reduce by 17 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 0 B
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. Markobrando.com has all CSS files already compressed.
Number of requests can be reduced by 14 (23%)
62
48
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Marko Brando. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
markobrando.com
681 ms
www.markobrando.com
874 ms
gtm.js
155 ms
style.css
653 ms
bootstrap.min.css
53 ms
all.min.css
69 ms
slick.css
76 ms
slick-theme.css
78 ms
aos.css
68 ms
js
120 ms
aos.css
19 ms
email-decode.min.js
54 ms
jquery-3.6.0.min.js
87 ms
bootstrap.bundle.min.js
52 ms
slick.min.js
52 ms
aos.js
54 ms
app.js
739 ms
aos.js
33 ms
css2
29 ms
css2
41 ms
marko-logo.webp
645 ms
logo.webp
627 ms
manubar.webp
744 ms
blkmanubar.webp
747 ms
bulb.webp
750 ms
plane.webp
759 ms
according.webp
1304 ms
buttonlines.webp
1456 ms
1.webp
1388 ms
2.webp
1345 ms
3.webp
1379 ms
4.0.webp
1401 ms
5.webp
1929 ms
6.webp
2041 ms
7.webp
2003 ms
8.webp
2025 ms
9.webp
2043 ms
10.webp
2065 ms
11.webp
2551 ms
12.webp
2626 ms
13.webp
2673 ms
14.webp
2653 ms
15.webp
2666 ms
16.webp
2689 ms
17.webp
3176 ms
18.webp
3245 ms
19.webp
3266 ms
20.webp
3288 ms
whitmail.webp
3924 ms
iconone.webp
3318 ms
indtwo.webp
3798 ms
myextraarrow.webp
3856 ms
GREYWALK.webp
4283 ms
BIBS.webp
3723 ms
DIAMOND.webp
4170 ms
LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_KUnNSg.ttf
214 ms
LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_TknNSg.ttf
251 ms
LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_d0nNSg.ttf
317 ms
LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_m07NSg.ttf
297 ms
LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_qU7NSg.ttf
317 ms
LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_907NSg.ttf
316 ms
LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_KU7NSg.ttf
351 ms
fa-solid-900.ttf
123 ms
fa-regular-400.ttf
178 ms
fa-brands-400.ttf
178 ms
MORYA.webp
4356 ms
ARIZTON.webp
4003 ms
yelow.webp
3856 ms
indmap1.webp
4199 ms
t1.png
4281 ms
t2.png
4373 ms
t3.png
4852 ms
t4.png
4089 ms
t5.png
4131 ms
t6.png
4400 ms
p1.webp
4482 ms
p2.webp
4342 ms
p3.webp
5176 ms
blogonei.webp
4216 ms
blogtwoi.webp
4420 ms
blogthree.webp
4543 ms
according.png
4535 ms
mail.webp
4476 ms
mobile.webp
4694 ms
map.webp
4488 ms
markobrando.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
markobrando.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
Browser errors were logged to the console
Page has valid source maps
markobrando.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Markobrando.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Markobrando.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.
markobrando.com
Open Graph description is not detected on the main page of Marko Brando. 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: