8.4 sec in total
1.7 sec
6.4 sec
337 ms
Welcome to homeplate.de homepage info - get ready to check Homeplate best content for Germany right away, or after learning these important things about homeplate.de
Herzlich Willkommen auf der Webseite der Roadrunners Berlin, dem einzigen Baseballverein im Osten von Berlin. Wir sind auch die Heimat der Prenzlberg Piranhas und der Red Peppers und spielen im Nordos...
Visit homeplate.deWe analyzed Homeplate.de page load time and found that the first response time was 1.7 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
homeplate.de performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value6.6 s
8/100
25%
Value16.5 s
0/100
10%
Value620 ms
48/100
30%
Value0
100/100
15%
Value23.9 s
1/100
10%
1656 ms
216 ms
575 ms
867 ms
736 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 56% of them (66 requests) were addressed to the original Homeplate.de, 14% (17 requests) were made to Maps.google.com and 8% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Homeplate.de.
Page size can be reduced by 522.2 kB (29%)
1.8 MB
1.3 MB
In fact, the total size of Homeplate.de main page is 1.8 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 60.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 60.8 kB or 81% of the original size.
Potential reduce by 137.8 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. Obviously, Homeplate needs image optimization as it can save up to 137.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 318.4 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 318.4 kB or 67% of the original size.
Potential reduce by 5.2 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. Homeplate.de needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 50% of the original size.
Number of requests can be reduced by 68 (61%)
111
43
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homeplate. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
homeplate.de
1656 ms
modal.css
216 ms
widgetkit-611dc8db.css
575 ms
bootstrap.css
867 ms
mootools-core.js
736 ms
core.js
221 ms
mootools-more.js
1289 ms
modal.js
543 ms
jquery.min.js
1079 ms
jquery-noconflict.js
759 ms
jquery-migrate.min.js
898 ms
widgetkit-3d3825fb.js
1165 ms
base.css
978 ms
layout.css
1089 ms
menus.css
1118 ms
modules.css
1337 ms
tools.css
1406 ms
system.css
1338 ms
extensions.css
1339 ms
custom.css
1375 ms
animation.css
1502 ms
blue.css
1529 ms
mavenpro.css
1531 ms
mavenpro.css
1558 ms
mavenpro.css
1496 ms
style.css
1638 ms
responsive.css
1618 ms
print.css
1641 ms
mavenpro.css
1651 ms
warp.js
1787 ms
responsive.js
1715 ms
accordionmenu.js
1838 ms
verticalDropdown.js
1965 ms
template.js
1855 ms
lightbox.js
853 ms
mediaelement-and-player.js
1128 ms
spotlight.js
777 ms
base.css
823 ms
layout.css
835 ms
menus.css
956 ms
modules.css
991 ms
system.css
1138 ms
system.css
1047 ms
system-all.css
1171 ms
tools.css
1100 ms
responsive.css
825 ms
print.css
862 ms
page.png
115 ms
logos_1090.jpg
527 ms
menu_dropdown_arrow.png
230 ms
menu_dropdown_level3.png
231 ms
IMG-20160205-WA0002.jpg
646 ms
IMG-20160205-WA0003.jpg
807 ms
Baseball_crop.png
976 ms
Bildschirmfoto_2015-11-17_um_13.08.56.png
1691 ms
Bildschirmfoto_2015-11-17_um_13.08.40.png
1756 ms
t_banner.jpg
741 ms
fslogoneu_frhp.jpg
1086 ms
TNKDLogo_web.jpg
1064 ms
logo_head.png
1468 ms
totop_scroller.png
1196 ms
Logo_alphaboard_300dpi_cymk.jpg
2436 ms
batting_web.jpg
1635 ms
slideshow.js
1581 ms
map.js
1833 ms
plusone.js
47 ms
all.js
5 ms
maven_pro_regular-webfont.woff
2077 ms
133 ms
xd_arbiter.php
31 ms
xd_arbiter.php
40 ms
cb=gapi.loaded_0
71 ms
cb=gapi.loaded_1
90 ms
fastbutton
129 ms
postmessageRelay
39 ms
cb=gapi.loaded_0
18 ms
cb=gapi.loaded_1
28 ms
3193398744-postmessagerelay.js
17 ms
rpc:shindig_random.js
45 ms
cb=gapi.loaded_0
11 ms
js
22 ms
common.js
4 ms
map.js
18 ms
util.js
16 ms
marker.js
17 ms
StaticMapService.GetMapImage
179 ms
onion.js
18 ms
openhand_8_8.cur
76 ms
ViewportInfoService.GetViewportInfo
72 ms
stats.js
19 ms
kh
62 ms
kh
61 ms
controls.js
10 ms
kh
53 ms
kh
51 ms
transparent.png
50 ms
css
54 ms
infowindow.js
42 ms
google4.png
45 ms
yellow-dot.png
43 ms
orange-dot.png
43 ms
blue-dot.png
44 ms
mapcnt6.png
45 ms
sv5.png
44 ms
vt
58 ms
vt
65 ms
vt
56 ms
vt
56 ms
tmapctrl.png
52 ms
cb_scout5.png
87 ms
tmapctrl4.png
52 ms
google_white5.png
53 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
49 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
51 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
79 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
79 ms
vt
53 ms
AuthenticationService.Authenticate
216 ms
homeplate.de 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
homeplate.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
homeplate.de 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Homeplate.de 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 Homeplate.de 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.
homeplate.de
Open Graph description is not detected on the main page of Homeplate. 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: