Access epiloguebookcafe.com. Bookstore & Coffee Shop in the heart of Chapel Hill

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value4,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

epiloguebookcafe.com

306 ms

www.epiloguebookcafe.com

187 ms

www.epiloguebookcafe.com

870 ms

uc.js

243 ms

system.js

17 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 23% of them (3 requests) were addressed to the original Epiloguebookcafe.com, 62% (8 requests) were made to Cdn3.editmysite.com and 8% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (870 ms) belongs to the original domain Epiloguebookcafe.com.

Content Size

688.9 kB

After Optimization

179.0 kB

In fact, the total size of Epiloguebookcafe.com main page is 688.9 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. 25% of websites need less resources to load. HTML takes 575.8 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 422.1 kB

Original 575.8 kB
After minification 574.9 kB
After compression 153.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 422.1 kB or 73% of the original size.

JavaScript Optimization

-78%

Potential reduce by 87.9 kB

Original 113.2 kB
After minification 113.2 kB
After compression 25.3 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 87.9 kB or 78% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epiloguebookcafe.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Epiloguebookcafe.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

Open Graph data is detected on the main page of Epilogue Bookcafe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: