4.5 sec in total
310 ms
4.1 sec
148 ms
Visit between.us now to see the best up-to-date Between content for United States and also check out these interesting facts you probably never knew about between.us
Between is a private space where you can share each moment only with that special someone. Create, share, and remember all your moments with each other. Get started now!
Visit between.usWe analyzed Between.us page load time and found that the first response time was 310 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
between.us performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value7.0 s
6/100
25%
Value7.3 s
28/100
10%
Value510 ms
57/100
30%
Value0.001
100/100
15%
Value10.1 s
26/100
10%
310 ms
892 ms
1053 ms
1193 ms
478 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 11% of them (6 requests) were addressed to the original Between.us, 53% (30 requests) were made to Dtqvguqpjeirn.cloudfront.net and 14% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Dtqvguqpjeirn.cloudfront.net.
Page size can be reduced by 711.6 kB (30%)
2.4 MB
1.7 MB
In fact, the total size of Between.us main page is 2.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 28.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. This page needs HTML code to be minified as it can gain 7.8 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 28.6 kB or 82% of the original size.
Potential reduce by 18.1 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. Between images are well optimized though.
Potential reduce by 301.6 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 301.6 kB or 63% of the original size.
Potential reduce by 363.3 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. Between.us needs all CSS files to be minified and compressed as it can save up to 363.3 kB or 84% of the original size.
Number of requests can be reduced by 25 (53%)
47
22
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Between. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
between.us
310 ms
between.us
892 ms
css.min.css
1053 ms
vendor.min.js
1193 ms
modernizr.min.js
478 ms
ga.js
28 ms
wcslog.js
44 ms
ga.js
159 ms
webfont.js
160 ms
logo_2x.png
177 ms
download_iphone_3x.png
177 ms
download_android_3x.png
181 ms
download_windows_3x.png
183 ms
download_mac_3x.png
184 ms
arrow.png
184 ms
main_bestapp_2x.png
190 ms
download_iphone_2x.png
183 ms
download_android_2x.png
190 ms
title_download_windows_2x.png
192 ms
title_download_mac_2x.png
192 ms
new_badge_2x.png
190 ms
main_zh_hans_2x.png
1521 ms
home_zh_hans_2x.png
1455 ms
profile_zh_hans_2x.png
1271 ms
moments_zh_hans_2x.png
1622 ms
chat_zh_hans_2x.png
1407 ms
calendar_zh_hans_2x.png
1336 ms
main_bestapp_mobile_2x.png
1273 ms
twitter_2x.png
1275 ms
facebook_2x.png
1279 ms
pinterest_2x.png
1281 ms
arrow.png
258 ms
tjaswtnR7bo
207 ms
main_bg.jpg
1241 ms
pr_bg.jpg
1254 ms
__utm.gif
125 ms
tjaswtnR7bo
154 ms
pager_inactive_2x.png
1178 ms
pager_active_2x.png
1179 ms
arrow_black.png
1182 ms
logo_mint_2x.png
1185 ms
arrow_right_2x.png
1185 ms
arrow_left_2x.png
1187 ms
m
1244 ms
notosanssc.css
76 ms
www-embed-player-vflQrT_sR.css
25 ms
www-embed-player.js
53 ms
NotoSansSC-Regular.woff
81 ms
NotoSansSC-Medium.woff
246 ms
NotoSansSC-Light.woff
329 ms
NotoSansSC-Thin.woff
389 ms
NotoSansSC-Bold.woff
390 ms
NotoSansSC-Black.woff
390 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
149 ms
ad_status.js
155 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
129 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
132 ms
between.us 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
Image elements do not have [alt] attributes
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>).
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.
between.us 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
between.us SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document doesn't have a valid hreflang
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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Between.us 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 Chinese language. Our system also found out that Between.us 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.
between.us
Open Graph data is detected on the main page of Between. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: