3.6 sec in total
772 ms
2.3 sec
490 ms
Welcome to same.to homepage info - get ready to check Same best content right away, or after learning these important things about same.to
LIFE IS ABOUT THE PEOPLE YOU MEET AND THE THINGS YOU CREATE WITH THEM. Find awesome people to share your trips, stays, and activities with!
Visit same.toWe analyzed Same.to page load time and found that the first response time was 772 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
same.to performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value11.6 s
0/100
25%
Value7.8 s
24/100
10%
Value470 ms
60/100
30%
Value0.026
100/100
15%
Value10.8 s
22/100
10%
772 ms
108 ms
208 ms
314 ms
23 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 69% of them (37 requests) were addressed to the original Same.to, 9% (5 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (926 ms) belongs to the original domain Same.to.
Page size can be reduced by 1.0 MB (30%)
3.5 MB
2.5 MB
In fact, the total size of Same.to main page is 3.5 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 107.7 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 107.7 kB or 77% of the original size.
Potential reduce by 107.3 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. Same images are well optimized though.
Potential reduce by 613.0 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 613.0 kB or 67% of the original size.
Potential reduce by 213.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. Same.to needs all CSS files to be minified and compressed as it can save up to 213.5 kB or 84% of the original size.
Number of requests can be reduced by 29 (60%)
48
19
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Same. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
same.to
772 ms
checkbox.min.css
108 ms
form.min.css
208 ms
bootstrap.min.css
314 ms
css
23 ms
font-awesome.min.css
215 ms
simple-line-icons.min.css
213 ms
animate.min.css
217 ms
owl.carousel.min.css
211 ms
nivo-lightbox.min.css
310 ms
default.min.css
323 ms
layout_4_light.css
344 ms
blue.css
331 ms
jquery.js
540 ms
jquery-migrate.min.js
420 ms
addthis_widget.js
15 ms
bootstrap.min.js
432 ms
retina.min.js
431 ms
smoothscroll.min.js
462 ms
wow.min.js
463 ms
jquery.nav.min.js
524 ms
nivo-lightbox.min.js
576 ms
jquery.stellar.min.js
575 ms
owl.carousel.min.js
577 ms
script.js
576 ms
comment-reply.min.js
671 ms
ga.js
78 ms
s-logo2-320.png
247 ms
same.png
244 ms
urban-438393_1920.jpg
926 ms
hero-phone2.png
913 ms
features-phone-310x530-310x530.png
788 ms
description-phone-front-265x550-265x550.png
448 ms
Eventuebersicht-245x435.png
547 ms
Eventdetail1-245x435.png
777 ms
Matches-245x435.png
780 ms
Chat-245x435.png
762 ms
subscribe-bg.jpg
365 ms
section-light-bg.png
855 ms
__utm.gif
69 ms
analytics.js
66 ms
boost
13 ms
300lo.json
62 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
48 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
145 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
145 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
145 ms
4cKlrioa77J2iqTqBgkRWg.ttf
146 ms
fontawesome-webfont.woff
690 ms
simple-line-icons.woff
797 ms
sh.07f0d9bf220d07a763adad1e.html
37 ms
collect
30 ms
layers.173914a8ea2767730b7b.js
29 ms
de.js
24 ms
same.to 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.
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
same.to 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
Issues were logged in the Issues panel in Chrome Devtools
same.to 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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Same.to 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 German language. Our system also found out that Same.to 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.
same.to
Open Graph data is detected on the main page of Same. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: