Tools & Wizards About Us
chicago68.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

chicago68.com

Chicago 1968 Democratic National Convention

Page Load Speed

516 ms in total

First Response

27 ms

Resources Loaded

361 ms

Page Rendered

128 ms

chicago68.com screenshot

About Website

Click here to check amazing Chicago 68 content. Otherwise, check out these important facts you probably never knew about chicago68.com

The antiwar protests and events in Chicago during the 1968 Democratic National Convention changed history. Chronology, bibliography, mythology, more.

Visit chicago68.com

Key Findings

We analyzed Chicago68.com page load time and found that the first response time was 27 ms and then it took 489 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

chicago68.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value2,540 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

chicago68.com

27 ms

chicago68.css

2 ms

js

79 ms

2y107TJ8ySBR8h5KTCbtVj

269 ms

hello.jpeg

6 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 14% of them (3 requests) were addressed to the original Chicago68.com, 76% (16 requests) were made to Embed-cdn.spotifycdn.com and 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (269 ms) relates to the external source Open.spotify.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.9 kB (1%)

Content Size

555.8 kB

After Optimization

549.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chicago68.com main page is 555.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. 60% of websites need less resources to load. Javascripts take 514.5 kB which makes up the majority of the site volume.

HTML Optimization

-55%

Potential reduce by 3.6 kB

  • Original 6.5 kB
  • After minification 6.3 kB
  • After compression 2.9 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 3.6 kB or 55% of the original size.

Image Optimization

-9%

Potential reduce by 1.8 kB

  • Original 20.7 kB
  • After minification 18.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. Chicago 68 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 233 B

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

CSS Optimization

-2%

Potential reduce by 320 B

  • Original 14.1 kB
  • After minification 14.1 kB
  • After compression 13.7 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. Chicago68.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (80%)

Requests Now

20

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chicago68.com

chicago68.com

27 ms

chicago68.css

chicago68.css

2 ms

js

js

79 ms

2y107TJ8ySBR8h5KTCbtVj

2y107TJ8ySBR8h5KTCbtVj

269 ms

hello.jpeg

hello.jpeg

6 ms

fd67e1fb69fabcc3.css

fd67e1fb69fabcc3.css

14 ms

d1ec150aabe345b6.css

d1ec150aabe345b6.css

16 ms

2dde3bebb2f7a1de.css

2dde3bebb2f7a1de.css

18 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

30 ms

webpack-b8481c5bb73de976.js

webpack-b8481c5bb73de976.js

43 ms

framework-160e3f4943d4ca83.js

framework-160e3f4943d4ca83.js

43 ms

main-db993876a962f8d0.js

main-db993876a962f8d0.js

29 ms

_app-b562e1a63be13baf.js

_app-b562e1a63be13baf.js

49 ms

fec483df-87a6891f9916661b.js

fec483df-87a6891f9916661b.js

51 ms

370d8c6a-ba7b9fa33b972102.js

370d8c6a-ba7b9fa33b972102.js

58 ms

2049-9d23dc857d07dafb.js

2049-9d23dc857d07dafb.js

59 ms

347-d1a541475d370b9c.js

347-d1a541475d370b9c.js

48 ms

3666-9b09ec6f6562685e.js

3666-9b09ec6f6562685e.js

48 ms

%5Bid%5D-65952c2341597590.js

%5Bid%5D-65952c2341597590.js

63 ms

_buildManifest.js

_buildManifest.js

64 ms

_ssgManifest.js

_ssgManifest.js

63 ms

Accessibility Review

chicago68.com accessibility score

80

Accessibility Issues

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.

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

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

chicago68.com SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chicago68.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 Chicago68.com main page’s claimed encoding is iso-8859-1. 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

chicago68.com

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