Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

cellar.apothic.com

Shop Red Wine, White Wine & Rosé | Apothic Wine

Page Load Speed

2.8 sec in total

First Response

40 ms

Resources Loaded

2.7 sec

Page Rendered

142 ms

About Website

Visit cellar.apothic.com now to see the best up-to-date Cellar Apothic content for United States and also check out these interesting facts you probably never knew about cellar.apothic.com

From rich red blends to a semi-sweet white and even a light rosé with dark secrets, Apothic makes wines that are anything but ordinary. Explore and Shop them all today.

Visit cellar.apothic.com

Key Findings

We analyzed Cellar.apothic.com page load time and found that the first response time was 40 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 55% of websites can load faster.

Performance Metrics

cellar.apothic.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value0.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

cellar.apothic.com

40 ms

cellar.apothic.com

206 ms

cellar.css

437 ms

satelliteLib-b17c692b2e3730d38d1475cab028e38f52f93a3c.js

186 ms

cellar-vendors.js

1105 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 48% of them (10 requests) were addressed to the original Cellar.apothic.com, 10% (2 requests) were made to Assets.adobedtm.com and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Cellar.apothic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.6 MB (82%)

Content Size

3.2 MB

After Optimization

577.4 kB

In fact, the total size of Cellar.apothic.com main page is 3.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. 20% of websites need less resources to load. Javascripts take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 26.0 kB

  • Original 36.0 kB
  • After minification 36.0 kB
  • After compression 10.0 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 26.0 kB or 72% of the original size.

JavaScript Optimization

-82%

Potential reduce by 2.6 MB

  • Original 3.1 MB
  • After minification 2.1 MB
  • After compression 567.4 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 2.6 MB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (42%)

Requests Now

12

After Optimization

7

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cellar Apothic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

cellar.apothic.com accessibility score

78

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

Document doesn't have a <title> element

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

cellar.apothic.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

cellar.apothic.com SEO score

55

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cellar.apothic.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 Cellar.apothic.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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