Tools & Wizards About Us
chicagocoffeescene.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

chicagocoffeescene.com

Coffee Blog | Coffee News, Reviews and more by Coffee Lovers

Page Load Speed

4.1 sec in total

First Response

1.3 sec

Resources Loaded

2.7 sec

Page Rendered

151 ms

chicagocoffeescene.com screenshot

About Website

Welcome to chicagocoffeescene.com homepage info - get ready to check Chicago Coffee Scene best content right away, or after learning these important things about chicagocoffeescene.com

Lissons is a coffee blog created by coffee lovers for coffee lovers. Coffee reviews on coffee blends, machines and accessories.

Visit chicagocoffeescene.com

Key Findings

We analyzed Chicagocoffeescene.com page load time and found that the first response time was 1.3 sec 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

chicagocoffeescene.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value7.1 s

30/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

lissons.co.uk

1329 ms

wp-emoji-release.min.js

311 ms

style.min.css

39 ms

wpforms-full.min.css

372 ms

simple-sitemap.css

33 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Chicagocoffeescene.com, 33% (16 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Lissons.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.2 kB (43%)

Content Size

232.8 kB

After Optimization

131.6 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 96.3 kB

  • Original 113.4 kB
  • After minification 106.6 kB
  • After compression 17.1 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 96.3 kB or 85% of the original size.

JavaScript Optimization

-0%

Potential reduce by 26 B

  • Original 51.1 kB
  • After minification 51.1 kB
  • After compression 51.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 4.9 kB

  • Original 68.3 kB
  • After minification 68.3 kB
  • After compression 63.4 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. Chicagocoffeescene.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

28

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

lissons.co.uk

lissons.co.uk

1329 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

311 ms

style.min.css

style.min.css

39 ms

wpforms-full.min.css

wpforms-full.min.css

372 ms

simple-sitemap.css

simple-sitemap.css

33 ms

style.css

style.css

30 ms

gutenverse-addons.css

gutenverse-addons.css

27 ms

fonts.css

fonts.css

308 ms

fontawesome.css

fontawesome.css

41 ms

style-mobile.css

style-mobile.css

47 ms

elementor-icons.min.css

elementor-icons.min.css

392 ms

frontend-lite.min.css

frontend-lite.min.css

544 ms

post-5.css

post-5.css

349 ms

global.css

global.css

504 ms

post-5349.css

post-5349.css

559 ms

css

css

91 ms

jquery.min.js

jquery.min.js

583 ms

jquery-migrate.min.js

jquery-migrate.min.js

684 ms

top-10-tracker.min.js

top-10-tracker.min.js

338 ms

ownScript.js

ownScript.js

350 ms

webpack.runtime.min.js

webpack.runtime.min.js

618 ms

frontend-modules.min.js

frontend-modules.min.js

768 ms

waypoints.min.js

waypoints.min.js

823 ms

core.min.js

core.min.js

783 ms

frontend.min.js

frontend.min.js

790 ms

underscore.min.js

underscore.min.js

1024 ms

wp-util.min.js

wp-util.min.js

876 ms

frontend.min.js

frontend.min.js

1041 ms

css

css

29 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

181 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

298 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

342 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

351 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

353 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

350 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

351 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

351 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

350 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

363 ms

fontello.woff

fontello.woff

365 ms

fa-solid-900.woff

fa-solid-900.woff

465 ms

fa-regular-400.woff

fa-regular-400.woff

433 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

358 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf

360 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

358 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

358 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

360 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

361 ms

Accessibility Review

chicagocoffeescene.com accessibility score

50

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

chicagocoffeescene.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

chicagocoffeescene.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

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 Chicagocoffeescene.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 Chicagocoffeescene.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

chicagocoffeescene.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: