6.6 sec in total
364 ms
4.8 sec
1.4 sec
Click here to check amazing Brixenmarathon content. Otherwise, check out these important facts you probably never knew about brixenmarathon.com
|||➤ running to the limits ➠ 5 Strecken ⛰️ 84 km ✓ 42 km ✓ 29 km ✓ 22km ✓ 4,2 km ➤ Das größte Laufwochenende in Südtirol ✅
Visit brixenmarathon.comWe analyzed Brixenmarathon.com page load time and found that the first response time was 364 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
brixenmarathon.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value12.9 s
0/100
25%
Value12.7 s
3/100
10%
Value680 ms
43/100
30%
Value0.26
47/100
15%
Value16.9 s
5/100
10%
364 ms
463 ms
662 ms
209 ms
320 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 98% of them (127 requests) were addressed to the original Brixenmarathon.com, 2% (3 requests) were made to Pro.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Brixenmarathon.com.
Page size can be reduced by 198.5 kB (3%)
6.9 MB
6.7 MB
In fact, the total size of Brixenmarathon.com main page is 6.9 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. Images take 6.6 MB which makes up the majority of the site volume.
Potential reduce by 197.9 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 197.9 kB or 83% of the original size.
Potential reduce by 562 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. Brixenmarathon images are well optimized though.
Number of requests can be reduced by 75 (65%)
116
41
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brixenmarathon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
brixenmarathon.com
364 ms
brixenmarathon.com
463 ms
www.brixenmarathon.com
662 ms
styles.css
209 ms
map-gpx-public.css
320 ms
style.min.css
323 ms
cookieblocker.min.css
328 ms
style.min.css
440 ms
style.css
328 ms
custom-frontend-lite.min.css
333 ms
post-3136.css
430 ms
leaflet.css
432 ms
mapbox-gl.css
452 ms
L.Icon.FontAwesome.css
452 ms
osm-map-elementor.css
454 ms
post-1082.css
535 ms
all.min.css
645 ms
simple-line-icons.min.css
547 ms
hamburgers.min.css
548 ms
collapse.css
549 ms
elementor-icons.min.css
558 ms
swiper.min.css
649 ms
post-1996.css
658 ms
custom-pro-frontend-lite.min.css
660 ms
post-491.css
662 ms
post-15739.css
671 ms
post-3168.css
756 ms
general.min.css
754 ms
widgets.css
773 ms
fontawesome.min.css
777 ms
brands.min.css
777 ms
solid.min.css
785 ms
jquery.min.js
877 ms
jquery-migrate.min.js
864 ms
map-gpx-public.js
890 ms
leaflet.js
1124 ms
mapbox-gl.js
1242 ms
leaflet-mapbox-gl.js
899 ms
custom-widget-icon-list.min.css
877 ms
custom-pro-widget-call-to-action.min.css
783 ms
all.css
794 ms
widget-carousel.min.css
698 ms
widget-posts.min.css
762 ms
custom-pro-widget-nav-menu.min.css
775 ms
style.min.css
809 ms
style.min.css
769 ms
style.min.css
780 ms
animations.min.css
775 ms
L.Icon.FontAwesome.js
791 ms
Leaflet.fullscreen.min.js
793 ms
imagesloaded.min.js
981 ms
theme.min.js
899 ms
drop-down-mobile-menu.min.js
891 ms
flickity.pkgd.min.js
893 ms
ow-slider.min.js
892 ms
scroll-effect.min.js
883 ms
select.min.js
794 ms
general.min.js
798 ms
complianz.min.js
789 ms
gpx-map-start-2.js
802 ms
function.js
817 ms
gpx-map-track-2.js
1144 ms
jquery.smartmenus.min.js
768 ms
webpack-pro.runtime.min.js
783 ms
webpack.runtime.min.js
779 ms
frontend-modules.min.js
796 ms
wp-polyfill-inert.min.js
814 ms
regenerator-runtime.min.js
835 ms
wp-polyfill.min.js
784 ms
hooks.min.js
773 ms
i18n.min.js
790 ms
frontend.min.js
804 ms
waypoints.min.js
770 ms
core.min.js
776 ms
frontend.min.js
759 ms
elements-handlers.min.js
709 ms
jquery.sticky.min.js
720 ms
lazyload.min.js
748 ms
lauefer-grau.png
525 ms
Linien-weiss.png
538 ms
Linien-weiss-rechts.png
559 ms
Roboto-Regular.woff
487 ms
Roboto-900.woff
486 ms
fa-brands-400.woff
809 ms
fa-brands-400.ttf
810 ms
eicons.woff
811 ms
leaflet.css
567 ms
leaflet.js
613 ms
fa-solid-900.woff
147 ms
fa-solid-900.ttf
447 ms
fa-regular-400.ttf
146 ms
Linien-grau.png
150 ms
Linien-blau-rechts.png
150 ms
Linien-blau-links.png
151 ms
geisler-spitzen.jpg
253 ms
fa-solid-900.woff
141 ms
fa-regular-400.woff
188 ms
fa-light-300.woff
189 ms
Linien-blau.png
112 ms
brixen-dolomiten-marathon.jpg
231 ms
logo-dolomites-ultra-trail.png
114 ms
logo-marathon.png
116 ms
logo-ladinia-trail.png
113 ms
logo-villnoess-dolomiten-run.png
116 ms
logo-womens-run-brixen.png
231 ms
ergebnisse-brixen-dolomiten-marathon.jpg
229 ms
teilnehmerfotos-trailrunning-villnoess.jpg
227 ms
trailrunning-news.jpg
345 ms
brixen-dolomiten-marathon-video.jpg
459 ms
loader.gif
340 ms
brixen-run.jpg
457 ms
villnoess-run.jpg
346 ms
gadertal-run.jpg
455 ms
trailrunning-dolomiten-04-768x512.jpg
564 ms
trailrunning-dolomiten-01-768x512.jpg
576 ms
trailrunning-dolomiten-07-768x511.jpg
462 ms
trailrunning-dolomiten-03-768x512.jpg
889 ms
trailrunning-dolomiten-05-768x512.jpg
579 ms
trailrunning-dolomiten-02-768x512.jpg
580 ms
trailrunning-dolomiten-06-768x512.jpg
689 ms
trailrunning-dolomiten-08-768x512.jpg
682 ms
trailrunning-dolomiten-09-768x511.jpg
691 ms
trailrunning-dolomiten-10-768x512.jpg
908 ms
trailrunning-dolomiten-11-768x511.jpg
695 ms
trailrunning-dolomiten-12-768x512.jpg
796 ms
suedtirol.jpg
801 ms
peitler-kofel-1024x341.png
806 ms
green-event.png
809 ms
martin-bacher-webdesign.png
908 ms
cancelled.jpg
915 ms
brixenmarathon.com accessibility score
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-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
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
Form elements do not have associated labels
Links do not have a discernible name
brixenmarathon.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
brixenmarathon.com SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brixenmarathon.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Brixenmarathon.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.
brixenmarathon.com
Open Graph data is detected on the main page of Brixenmarathon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: