1.8 sec in total
165 ms
1.1 sec
492 ms
Click here to check amazing Bttl content for Russia. Otherwise, check out these important facts you probably never knew about bttl.me
#1 mobile app for rap battles. Compete with friends and strangers in rap battles, and the community will choose the winner!
Visit bttl.meWe analyzed Bttl.me page load time and found that the first response time was 165 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
bttl.me performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value13.6 s
0/100
25%
Value10.6 s
7/100
10%
Value22,580 ms
0/100
30%
Value0.357
30/100
15%
Value32.6 s
0/100
10%
165 ms
133 ms
127 ms
44 ms
48 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 60% of them (38 requests) were addressed to the original Bttl.me, 13% (8 requests) were made to Youtube.com and 11% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (638 ms) belongs to the original domain Bttl.me.
Page size can be reduced by 376.9 kB (17%)
2.2 MB
1.8 MB
In fact, the total size of Bttl.me main page is 2.2 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 11.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 11.8 kB or 72% of the original size.
Potential reduce by 7.9 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. Bttl images are well optimized though.
Potential reduce by 45.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 45.7 kB or 29% of the original size.
Potential reduce by 311.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. Bttl.me needs all CSS files to be minified and compressed as it can save up to 311.5 kB or 82% of the original size.
Number of requests can be reduced by 27 (51%)
53
26
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bttl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
bttl.me
165 ms
style.css
133 ms
responsive.css
127 ms
css
44 ms
font-awesome.min.css
48 ms
layerslider.css
136 ms
lightbox.css
120 ms
component.css
171 ms
email-decode.min.js
9 ms
jquery-2.1.1.min.js
31 ms
greensock.js
127 ms
layerslider.js
185 ms
layerslider.kreaturamedia.js
213 ms
lightbox.js
259 ms
jquery.shuffle.js
260 ms
modernizr.js
267 ms
classie.js
266 ms
modalEffects.js
274 ms
app.js
288 ms
youtube-autoresizer.js
32 ms
player_api
49 ms
U-Kd9sLpPOY
127 ms
close.png
161 ms
loading.gif
188 ms
prev.png
207 ms
next.png
207 ms
header-bg.jpg
206 ms
sh_fullsize_distr.png
206 ms
hand_iphone_x.png
231 ms
tri-white-top.png
233 ms
01_screen_beat.png
417 ms
02_screen_studio.png
419 ms
04_screen_profile.png
416 ms
07_screen_hero.png
418 ms
05_screen_tournaments.png
419 ms
06_screen_feed.png
420 ms
03_screen_judge.png
421 ms
tri-white-bot.png
422 ms
bg-texture2_n.jpg
602 ms
google-play-badge.png
638 ms
appstore-badge.png
637 ms
Second_pic1.png
638 ms
background_n.jpg
637 ms
www-player.css
50 ms
www-embed-player.js
74 ms
base.js
151 ms
fetch-polyfill.js
17 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
114 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
135 ms
KFOmCnqEu92Fr1Mu4mxM.woff
139 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
318 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
318 ms
fontawesome-webfont.woff
110 ms
www-widgetapi.js
77 ms
analytics.js
102 ms
skin.css
504 ms
collect
186 ms
ad_status.js
269 ms
nrTPYF1MeWhW5u-1uricHJVJdskICRuFTkjv60UEiAs.js
152 ms
embed.js
48 ms
KFOmCnqEu92Fr1Mu4mxM.woff
33 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
34 ms
id
27 ms
bttl.me 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
Image elements do not have [alt] attributes
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.
bttl.me 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
bttl.me 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bttl.me can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Bttl.me 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.
bttl.me
Open Graph description is not detected on the main page of Bttl. 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: