4 sec in total
503 ms
3.3 sec
183 ms
Click here to check amazing Brave Brain content for Poland. Otherwise, check out these important facts you probably never knew about bravebrain.pl
Agencja reklamowa, która tworzy marki warte zapamiętania. Specjalizujemy się w brandingu, kampaniach 360, projektowaniu opakowań.
Visit bravebrain.plWe analyzed Bravebrain.pl page load time and found that the first response time was 503 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
bravebrain.pl performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value14.2 s
0/100
25%
Value7.0 s
32/100
10%
Value960 ms
29/100
30%
Value0
100/100
15%
Value8.3 s
39/100
10%
503 ms
116 ms
389 ms
227 ms
514 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 94% of them (67 requests) were addressed to the original Bravebrain.pl, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Bravebrain.pl.
Page size can be reduced by 460.6 kB (32%)
1.4 MB
989.3 kB
In fact, the total size of Bravebrain.pl 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. 60% of websites need less resources to load. Images take 862.7 kB which makes up the majority of the site volume.
Potential reduce by 26.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. 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 26.8 kB or 77% of the original size.
Potential reduce by 33.3 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. Brave Brain images are well optimized though.
Potential reduce by 254.6 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 254.6 kB or 68% of the original size.
Potential reduce by 145.9 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. Bravebrain.pl needs all CSS files to be minified and compressed as it can save up to 145.9 kB or 82% of the original size.
Number of requests can be reduced by 22 (35%)
63
41
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brave Brain. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
bravebrain.pl
503 ms
css_PpiQEI-azlEmknynFVbTW6pWwXhVPT_fbABYbBL6JWQ.css
116 ms
css_-5kH_qNKfQwdp3Ga2DprUJQeIE6pSauAqf-DwbpF22s.css
389 ms
css_w1LAgwE0vKMzZDmPsymyKwJjHPbGgRPf0Ceu3-fAUhg.css
227 ms
css_Y4KXNMYl4DkNr54K7tcMj38GO597jgZB0UaGT6d7VbA.css
514 ms
warnCookies.js
396 ms
jquery.min.js
551 ms
bootstrap.min.js
402 ms
jquery.slimscroll.js
385 ms
jquery.fullPage.min.js
498 ms
modernizr.custom.js
496 ms
classie.js
549 ms
overlay.js
548 ms
TweenLite.min.js
609 ms
EasePack.min.js
615 ms
rAF.js
627 ms
canvas.js
628 ms
jquery.js
753 ms
jquery.once.js
740 ms
drupal.js
742 ms
jquery.cookie.js
740 ms
pl_7qT7bEtfmXqPmfANHHBQCUqNqMAXuE49U1pHSYib2x0.js
745 ms
textarea.js
745 ms
googleanalytics.js
752 ms
logo.png
955 ms
brave-ideas-only.png
305 ms
o-nas.png
341 ms
dot-red.png
341 ms
brave-brain-nagorody.jpg
341 ms
o-nas-up.jpg
343 ms
co-robimy.png
426 ms
feature-kampanie-reklamowe.png
459 ms
feature-strategie-marketingowe.png
459 ms
feature-branding.png
474 ms
feature-strony-www.png
474 ms
feature-aplikacje-mobilne.png
530 ms
feature-mobile-marketing.png
530 ms
feature-strategie-pr.png
579 ms
feature-social-media.png
579 ms
feature-wideo-animacja.png
582 ms
portfolio.png
582 ms
cross-red-bg.png
641 ms
kontakt.png
642 ms
icon-location.png
704 ms
icon-phone.png
696 ms
logo.png
691 ms
bg-home-gradient.jpg
1268 ms
bg-onas-gradient.jpg
1284 ms
OpenSans-Regular-webfont.woff
852 ms
OpenSans-Bold-webfont.woff
960 ms
NexaBold.otf
846 ms
NexaLight.otf
727 ms
fontawesome-webfont.woff
970 ms
bg-what-we-do-gradient.jpg
1203 ms
bg-portfolio.jpg
1073 ms
1.jpg
1414 ms
3.jpg
1187 ms
2.jpg
1297 ms
analytics.js
61 ms
4.jpg
1244 ms
5.jpg
1475 ms
collect
13 ms
wisla-krakow-bg.jpg
1224 ms
collect
64 ms
castel-bg.jpg
1413 ms
good-ride.jpg
1414 ms
sinevia-bg.jpg
1413 ms
budner_0.jpg
1646 ms
ga-audiences
50 ms
dowiedz-sie-wiecej-4_0.png
1326 ms
bg-contact-gradient.jpg
1786 ms
bravebrain.pl 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
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
bravebrain.pl 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
bravebrain.pl 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
Tap targets are not sized appropriately
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bravebrain.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Bravebrain.pl 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.
bravebrain.pl
Open Graph description is not detected on the main page of Brave Brain. 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: