8.4 sec in total
1.5 sec
5.6 sec
1.4 sec
Visit iheartberlin.de now to see the best up-to-date IHeartBerlin content for Germany and also check out these interesting facts you probably never knew about iheartberlin.de
Visit iheartberlin.deWe analyzed Iheartberlin.de page load time and found that the first response time was 1.5 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
iheartberlin.de performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value10.3 s
0/100
25%
Value14.8 s
1/100
10%
Value1,030 ms
26/100
30%
Value0.26
47/100
15%
Value17.7 s
4/100
10%
1473 ms
186 ms
272 ms
295 ms
292 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 91% of them (109 requests) were addressed to the original Iheartberlin.de, 3% (3 requests) were made to Use.fontawesome.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Iheartberlin.de.
Page size can be reduced by 1.1 MB (7%)
15.6 MB
14.4 MB
In fact, the total size of Iheartberlin.de main page is 15.6 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 14.3 MB which makes up the majority of the site volume.
Potential reduce by 295.6 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 295.6 kB or 83% of the original size.
Potential reduce by 740.6 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. IHeartBerlin images are well optimized though.
Potential reduce by 99.7 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 99.7 kB or 12% of the original size.
Potential reduce by 1.5 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. Iheartberlin.de has all CSS files already compressed.
Number of requests can be reduced by 88 (76%)
116
28
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IHeartBerlin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 70 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.iheartberlin.de
1473 ms
styles.css
186 ms
main.css
272 ms
schlange.css
295 ms
tree.js
292 ms
ayecode-ui-compatibility.css
384 ms
style.css
289 ms
woocommerce-layout.css
310 ms
woocommerce.css
377 ms
css
51 ms
layout-styles.css
396 ms
front.css
400 ms
all.css
48 ms
style.css
402 ms
jquery.min.js
497 ms
jquery-migrate.min.js
476 ms
widget.min.js
479 ms
wp-polyfill-inert.min.js
511 ms
regenerator-runtime.min.js
513 ms
wp-polyfill.min.js
600 ms
hooks.min.js
574 ms
w.js
32 ms
select2.min.js
581 ms
bootstrap.bundle.min.js
625 ms
geodirectory.min.js
549 ms
common.min.js
559 ms
front.min.js
592 ms
jquery.blockUI.min.js
603 ms
add-to-cart.min.js
634 ms
js.cookie.min.js
627 ms
woocommerce.min.js
636 ms
front.min.js
723 ms
et-divi-customizer-global.min.css
688 ms
classic-10_7_dtp.css
37 ms
mc-validate.js
51 ms
wc-blocks.css
705 ms
mediaelementplayer-legacy.min.css
815 ms
wp-mediaelement.min.css
816 ms
js
76 ms
oms.min.js
816 ms
goMap.min.js
816 ms
sourcebuster.min.js
817 ms
e-202419.js
33 ms
order-attribution.min.js
870 ms
react.min.js
778 ms
deprecated.min.js
691 ms
dom.min.js
673 ms
react-dom.min.js
770 ms
escape-html.min.js
688 ms
element.min.js
746 ms
is-shallow-equal.min.js
678 ms
i18n.min.js
653 ms
keycodes.min.js
651 ms
priority-queue.min.js
691 ms
compose.min.js
742 ms
private-apis.min.js
679 ms
redux-routine.min.js
672 ms
data.min.js
648 ms
lodash.min.js
641 ms
wc-blocks-registry.js
674 ms
url.min.js
683 ms
api-fetch.min.js
683 ms
g.gif
23 ms
wc-settings.js
637 ms
data-controls.min.js
624 ms
html-entities.min.js
624 ms
notices.min.js
654 ms
wc-blocks-middleware.js
690 ms
wc-blocks-data.js
691 ms
dom-ready.min.js
657 ms
a11y.min.js
656 ms
primitives.min.js
663 ms
warning.min.js
629 ms
blocks-components.js
683 ms
blocks-checkout.js
671 ms
order-attribution-blocks.min.js
594 ms
scripts.min.js
675 ms
jquery.fitvids.js
593 ms
jquery.mobile.js
596 ms
easypiechart.js
667 ms
font
82 ms
fa-solid-900.ttf
56 ms
fa-regular-400.ttf
80 ms
salvattore.js
637 ms
common.js
640 ms
mediaelement-and-player.min.js
644 ms
mediaelement-migrate.min.js
708 ms
leaflet.css
676 ms
leaflet-routing-machine.css
631 ms
wp-mediaelement.min.js
653 ms
modules.woff
842 ms
leaflet.min.js
655 ms
osm.geocode.min.js
709 ms
leaflet-routing-machine.min.js
684 ms
oms-leaflet.min.js
621 ms
gb.png
739 ms
de.png
739 ms
iHeartBerlin-Logo-2020-neon.png
738 ms
preloader.gif
736 ms
16-copy-2-768x960.jpg
963 ms
Bildschirmfoto-2024-05-02-um-01.08.35.png
903 ms
The-Future-von-Constanza-Macras-DorkyPark-768x511.jpeg
910 ms
adam_munnings_death_drive_in_graded_5-1-768x768.jpg
1102 ms
lipsync-768x887.jpg
965 ms
GearsGlass_Insta1x1-768x768.jpg
1047 ms
Brave-New-Fashion-5-400x250.png
964 ms
Deckhengst.jpg
903 ms
Bruderkuss-Mural.jpg
912 ms
Brave-New-Fashion-5-1080x675.png
1051 ms
01A5095-400x250.jpg
989 ms
boatsex-400x250.jpg
987 ms
Kindl-exhibition-view-photo-Marco-Funke.jpg
980 ms
01A5095-1080x675.jpg
1023 ms
boatsex-1080x675.jpg
975 ms
IHB-Collection-Monopol-3949.jpg
1066 ms
christina-spiliotopoulou-LgwMDV64aOg-unsplash-scaled.jpg
1158 ms
moet_DSCF6444_v1.jpg
1104 ms
IHB-Collection-3941.jpg
684 ms
Logoglitch.jpg
649 ms
woocommerce-smallscreen.css
98 ms
iheartberlin.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.
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.
iheartberlin.de 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
Browser errors were logged to the console
iheartberlin.de 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
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 Iheartberlin.de 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 Iheartberlin.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.
iheartberlin.de
Open Graph description is not detected on the main page of IHeartBerlin. 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: