4.2 sec in total
336 ms
3.5 sec
396 ms
Welcome to cogether.de homepage info - get ready to check Cogether best content for Germany right away, or after learning these important things about cogether.de
Ratgeber und Tipps für die Hochzeit. Für Brautpaare, Trauzeugen und Hochzeitsgäste. Finden Sie alles, was Sie für die Hochzeit brauchen.
Visit cogether.deWe analyzed Cogether.de page load time and found that the first response time was 336 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
cogether.de performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
336 ms
350 ms
338 ms
644 ms
329 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cogether.de, 18% (26 requests) were made to Static.xx.fbcdn.net and 18% (26 requests) were made to Hochzeitsportal24.de. The less responsive or slowest element that took the longest time to load (977 ms) relates to the external source App.weddian.de.
Page size can be reduced by 1.5 MB (50%)
3.1 MB
1.6 MB
In fact, the total size of Cogether.de main page is 3.1 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. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 51.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 51.6 kB or 74% of the original size.
Potential reduce by 16.7 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. Cogether images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 67% of the original size.
Potential reduce by 455.6 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. Cogether.de needs all CSS files to be minified and compressed as it can save up to 455.6 kB or 90% of the original size.
Number of requests can be reduced by 67 (50%)
133
66
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cogether. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
cogether.de
336 ms
www.hochzeitsportal24.de
350 ms
app.css
338 ms
app.js
644 ms
jquery.js
329 ms
jquery-migrate.min.js
245 ms
affiliate-power.js
244 ms
load.sumome.com
372 ms
3910580465.js
52 ms
immer_oben.js
776 ms
ivw.js
580 ms
conversion.js
24 ms
wp-embed.min.js
239 ms
js
60 ms
css
26 ms
bg.png
447 ms
logo.png
113 ms
fabalista.png
111 ms
hochzeitsportal24_2.jpg
108 ms
sonjaPortrait.jpg
110 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
28 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
28 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
28 ms
iam.js
394 ms
fpc.pl
37 ms
438 ms
qs.ioam.de
298 ms
tx.io
211 ms
a
63 ms
429 ms
430 ms
432 ms
yi
126 ms
ankecallig-fg-webfont.woff
235 ms
fontawesome-webfont.woff
331 ms
Fotolia_45973335_Subscription_L.jpg
325 ms
Hochzeitsdeko-700x350.jpg
212 ms
show_ads.js
192 ms
hochzeitsfeuerwerk-700x350.jpg
233 ms
Heiraten-Holland-Strand-700x350.jpg
233 ms
Hochzeitstorte-anschneiden-700x350.jpg
408 ms
Musik-kirchliche-Trauung-Gospel-700x350.jpg
544 ms
Garten-Hochzeit-700x276.jpg
539 ms
Braeute-Treffen-700x350.jpg
481 ms
einladungskarten.png
430 ms
gtm.js
107 ms
sdk.js
87 ms
105 ms
searchForm.html
385 ms
269 ms
Depositphotos_35137565_original.jpg
649 ms
Fotolia_52124361_Subscription_XL.jpg
652 ms
tx.io
107 ms
68 ms
142 ms
fbds.js
4 ms
analytics.js
29 ms
xd_arbiter.php
48 ms
xd_arbiter.php
54 ms
145 ms
linkid.js
21 ms
ads-async.js
71 ms
collect
14 ms
collect
67 ms
100checklisten.jpg
86 ms
impression.gif
69 ms
ga-audiences
18 ms
multi-cookie.gif
75 ms
service.js
12 ms
service.js
26 ms
sme-popup.css
6 ms
sumome-smartbar-popup.css
8 ms
css
48 ms
load
261 ms
load
276 ms
common.js
42 ms
util.js
58 ms
controls.js
68 ms
places_impl.js
69 ms
withSlug
977 ms
87 ms
72 ms
148 ms
164 ms
transparent-crown-light.png
175 ms
like.php
87 ms
TY3MhkXpWJ-.js
53 ms
LVx-xkvaJ0b.png
29 ms
collect
5 ms
22 ms
page.php
431 ms
Ezryo55Cca5.css
16 ms
HKna9a9CcB_.css
12 ms
m3UplzJmRpp.css
21 ms
2xgrlpxBmsP.css
22 ms
ugvD9E8vfHH.css
22 ms
1kPfZUdGrka.js
31 ms
HQ1UKbUXIBt.js
43 ms
Qd7TTBR3F_S.js
42 ms
1dEEvSwLtg5.js
42 ms
b1o_4KKMvfn.js
52 ms
TzWCmQ2GDUt.js
41 ms
R5mDVFPVP4X.js
63 ms
k3HgkHYQ8wO.js
63 ms
11822525_974830105900872_2701598994009082913_n.jpg
128 ms
safe_image.php
140 ms
102 ms
safe_image.php
82 ms
safe_image.php
83 ms
safe_image.php
80 ms
safe_image.php
80 ms
safe_image.php
90 ms
safe_image.php
111 ms
safe_image.php
84 ms
safe_image.php
85 ms
safe_image.php
86 ms
safe_image.php
88 ms
safe_image.php
88 ms
11057365_974829812567568_5464421864225934624_n.jpg
75 ms
431950_830668593711788_8898393900725128955_n.jpg
68 ms
1379841_10150004552801901_469209496895221757_n.jpg
72 ms
10408011_673967782674540_3687564803851867262_n.jpg
75 ms
12039590_916782558386868_7453918711376511661_n.jpg
73 ms
12552991_202363643449865_5628764491639546556_n.jpg
73 ms
12552769_1687885894758129_3964950003149985975_n.jpg
73 ms
12718293_967300330014608_4140645909549161589_n.jpg
80 ms
11825922_1025252720827090_4923965377180875535_n.jpg
78 ms
12733983_808387662600742_2050095327535220385_n.jpg
109 ms
12249808_1156220324396022_4973064564141836661_n.jpg
78 ms
9592_451097545088322_7193023816429798227_n.jpg
77 ms
11011079_1512680629055814_8167603165641040489_n.jpg
106 ms
12651260_455973081262097_4316529017595686884_n.jpg
93 ms
11057365_974829812567568_5464421864225934624_n.jpg
81 ms
wL6VQj7Ab77.png
62 ms
s7jcwEQH7Sx.png
63 ms
GtIpNnEyqq_.png
63 ms
L0X3j16BFLW.png
62 ms
YzFEFmGRSUa.png
63 ms
-t9F9Q_9QnC.png
62 ms
jWwyUJH0aOO.js
68 ms
R9GKCzjAnbk.js
6 ms
AWWjhOengNF.js
6 ms
YnSasnyq68i.js
10 ms
kQf_jlUv-kX.js
6 ms
cogether.de accessibility score
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
cogether.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
cogether.de SEO score
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cogether.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 Cogether.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.
cogether.de
Open Graph data is detected on the main page of Cogether. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: