10.1 sec in total
244 ms
9 sec
903 ms
Welcome to brianvanandel.com homepage info - get ready to check Brianvanandel best content right away, or after learning these important things about brianvanandel.com
https://brianvanandel.com/wp-content/uploads/2022/07/Brian-van-Andel-Show-2019.mp4 Tomorrowland 2022 PHOTOS Anterior Siguiente MUSIC NEW VIDEO ABOUT When talking about Brian van Andel, we refer to tec...
Visit brianvanandel.comWe analyzed Brianvanandel.com page load time and found that the first response time was 244 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
brianvanandel.com performance score
name
value
score
weighting
Value17.9 s
0/100
10%
Value37.5 s
0/100
25%
Value38.9 s
0/100
10%
Value39,480 ms
0/100
30%
Value0.32
36/100
15%
Value68.7 s
0/100
10%
244 ms
6258 ms
403 ms
502 ms
307 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 91% of them (95 requests) were addressed to the original Brianvanandel.com, 5% (5 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Brianvanandel.com.
Page size can be reduced by 2.1 MB (37%)
5.7 MB
3.6 MB
In fact, the total size of Brianvanandel.com main page is 5.7 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. 65% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 102.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 102.0 kB or 80% of the original size.
Potential reduce by 15.1 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. Brianvanandel images are well optimized though.
Potential reduce by 176.2 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 176.2 kB or 68% of the original size.
Potential reduce by 1.8 MB
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. Brianvanandel.com needs all CSS files to be minified and compressed as it can save up to 1.8 MB or 86% of the original size.
Number of requests can be reduced by 77 (82%)
94
17
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brianvanandel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
brianvanandel.com
244 ms
brianvanandel.com
6258 ms
wp-emoji-release.min.js
403 ms
dashicons.min.css
502 ms
thickbox.css
307 ms
sbi-styles.min.css
412 ms
style.min.css
514 ms
settings.css
311 ms
fontello.css
329 ms
rs6.css
518 ms
frontend-legacy.min.css
427 ms
frontend.min.css
727 ms
sonaar-addons-elementor.css
538 ms
fontawesome.min.css
525 ms
brands.min.css
528 ms
solid.min.css
540 ms
regular.min.css
623 ms
js_composer.min.css
1416 ms
classic.css
628 ms
main.min.css
1150 ms
ie.css
652 ms
elementor-icons.min.css
731 ms
post-2745.css
732 ms
frontend.min.css
1171 ms
all.min.css
828 ms
v4-shims.min.css
833 ms
global.css
831 ms
post-2792.css
930 ms
brianvanandel.com
1432 ms
mediaelementplayer-legacy.min.css
939 ms
wp-mediaelement.min.css
1031 ms
css
28 ms
jquery.min.js
1145 ms
jquery-migrate.min.js
1134 ms
rbtools.min.js
1240 ms
rs6.min.js
1486 ms
v4-shims.min.js
1256 ms
font-awesome.min.css
1070 ms
vue.min.js
36 ms
d3.min.js
96 ms
api.js
44 ms
animations.min.css
1138 ms
thickbox.js
1138 ms
regenerator-runtime.min.js
1066 ms
wp-polyfill.min.js
1121 ms
index.js
1193 ms
jquery.countdown-es.js
1187 ms
underscore.min.js
1146 ms
core.min.js
1143 ms
mouse.min.js
1133 ms
slider.min.js
1050 ms
mediaelement-and-player.min.js
1249 ms
mediaelement-migrate.min.js
1088 ms
js_composer_front.min.js
1081 ms
sonaar.scripts.min.js
1386 ms
classic.min.js
1022 ms
jquery.plugin.min.js
1038 ms
jquery.countdown.min.js
1039 ms
index.js
992 ms
wp-mediaelement.min.js
1017 ms
vimeo.min.js
1041 ms
sonaar-addons-elementor.min.js
976 ms
webpack-pro.runtime.min.js
992 ms
webpack.runtime.min.js
1016 ms
frontend-modules.min.js
949 ms
hooks.min.js
940 ms
i18n.min.js
867 ms
frontend.min.js
873 ms
waypoints.min.js
863 ms
swiper.min.js
840 ms
share-link.min.js
818 ms
dialog.min.js
769 ms
frontend.min.js
768 ms
preloaded-elements-handlers.min.js
954 ms
preloaded-modules.min.js
726 ms
jquery.sticky.min.js
729 ms
css
13 ms
css
16 ms
css
19 ms
css
20 ms
D786E317-979D-4640-BDF5-7AB34084EC1E-2-1024x1024.jpg
678 ms
D070ADD9-6E0C-40FA-8D56-CE83BC2E882E-3-1024x1024.jpg
594 ms
Portada-foto-Medusa-web-1-1024x717.jpg
613 ms
220716-163423-TML2022-DN100396-DN-1024x576.jpg
762 ms
Brian-van-Andel-_-Arenal-Sound-2-1-1024x683.jpg
678 ms
Brian-van-Andel-_-Arenal-Sound-6-1024x683.jpg
699 ms
Brian-van-Andel-Medusa-2019-1024x683.jpg
714 ms
Foto-Portada-1024x717.png
943 ms
A7D6BFD9-88A7-489A-B6FD-9B8FE9CAE25C-1024x683.jpg
737 ms
defaultpx.png
754 ms
eicons.woff
793 ms
fa-regular-400.woff
738 ms
fa-regular-400.woff
768 ms
fa-solid-900.woff
781 ms
fa-solid-900.woff
789 ms
fa-brands-400.woff
777 ms
fa-brands-400.woff
770 ms
fontawesome-webfont.woff
762 ms
Logo-Web4.png
762 ms
Brian-van-Andel-_-Arenal-Sound-2018-3.jpg
754 ms
recaptcha__en.js
30 ms
Frame-1-3-559x559.png
561 ms
loadingAnimation.gif
292 ms
Logo-Horizontal-Brian-van-Andel-White.png
107 ms
brianvanandel.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
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.
brianvanandel.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
brianvanandel.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
Tap targets are not sized appropriately
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brianvanandel.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Brianvanandel.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.
brianvanandel.com
Open Graph data is detected on the main page of Brianvanandel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: