Tools & Wizards About Us
drinkeer.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

drinkeer.com

Drinkeer

Page Load Speed

4.1 sec in total

First Response

1.5 sec

Resources Loaded

2.5 sec

Page Rendered

113 ms

drinkeer.com screenshot

About Website

Welcome to drinkeer.com homepage info - get ready to check Drinkeer best content right away, or after learning these important things about drinkeer.com

Drinkeer, the first drink sharing site in the world. You can instantly share your drink, make cheers to people and make new friends.

Visit drinkeer.com

Key Findings

We analyzed Drinkeer.com page load time and found that the first response time was 1.5 sec and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

drinkeer.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

drinkeer.com

1524 ms

reset.css

149 ms

style.css

151 ms

landing.css

151 ms

index.css

150 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 60% of them (29 requests) were addressed to the original Drinkeer.com, 10% (5 requests) were made to Youtube.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Drinkeer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.8 kB (23%)

Content Size

807.3 kB

After Optimization

625.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Drinkeer.com main page is 807.3 kB. 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 410.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 16.9 kB

  • Original 22.2 kB
  • After minification 20.6 kB
  • After compression 5.2 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 16.9 kB or 76% of the original size.

Image Optimization

-19%

Potential reduce by 77.2 kB

  • Original 410.0 kB
  • After minification 332.8 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. Obviously, Drinkeer needs image optimization as it can save up to 77.2 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 76.2 kB

  • Original 300.0 kB
  • After minification 298.6 kB
  • After compression 223.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 76.2 kB or 25% of the original size.

CSS Optimization

-15%

Potential reduce by 11.4 kB

  • Original 75.2 kB
  • After minification 74.8 kB
  • After compression 63.8 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. Drinkeer.com needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (59%)

Requests Now

44

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drinkeer. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

drinkeer.com

drinkeer.com

1524 ms

reset.css

reset.css

149 ms

style.css

style.css

151 ms

landing.css

landing.css

151 ms

index.css

index.css

150 ms

top-menu.css

top-menu.css

75 ms

custom-file-input.css

custom-file-input.css

76 ms

sprites-1.css

sprites-1.css

76 ms

analytics.js

analytics.js

13 ms

atrk.js

atrk.js

13 ms

1pES5OnIbHM

1pES5OnIbHM

149 ms

landing-bg.png

landing-bg.png

102 ms

landing-top-bg.png

landing-top-bg.png

213 ms

top-bg.png

top-bg.png

102 ms

sprites-1.png

sprites-1.png

605 ms

triangle-3.png

triangle-3.png

605 ms

sdk.js

sdk.js

50 ms

collect

collect

65 ms

sdk.js

sdk.js

8 ms

46 ms

js

js

106 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

32 ms

base.js

base.js

69 ms

ad_status.js

ad_status.js

220 ms

yLH_7IXO2IqaYUCpWhi8UlTKCOG5A1JfiUQGnHrKDOk.js

yLH_7IXO2IqaYUCpWhi8UlTKCOG5A1JfiUQGnHrKDOk.js

137 ms

embed.js

embed.js

37 ms

id

id

29 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

147 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

148 ms

Create

Create

117 ms

GenerateIT

GenerateIT

12 ms

sample-share-body.png

sample-share-body.png

77 ms

other_62_78.png

other_62_78.png

75 ms

41464_80_80.jpg

41464_80_80.jpg

76 ms

jquery.min.js

jquery.min.js

369 ms

jquery.button.min.js

jquery.button.min.js

76 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

77 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

147 ms

jquery.validate.min.js

jquery.validate.min.js

148 ms

moment.min.js

moment.min.js

147 ms

en.js

en.js

147 ms

landing-common.js

landing-common.js

149 ms

sample-share.js

sample-share.js

219 ms

index.js

index.js

220 ms

landing-footer-bg.png

landing-footer-bg.png

221 ms

config.js

config.js

289 ms

sprites.png

sprites.png

589 ms

Accessibility Review

drinkeer.com accessibility score

83

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

drinkeer.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

drinkeer.com SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drinkeer.com 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 Drinkeer.com 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.

Social Sharing Optimization

drinkeer.com

Open Graph description is not detected on the main page of Drinkeer. 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: