Tools & Wizards About Us

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

circa1886.com

Charleston Historic District Fine Dining Restaurant | Circa 1886

Page Load Speed

4.1 sec in total

First Response

197 ms

Resources Loaded

2.5 sec

Page Rendered

1.3 sec

About Website

Visit circa1886.com now to see the best up-to-date Circa 1886 content for United States and also check out these interesting facts you probably never knew about circa1886.com

Tucked within the original carriage house of Wentworth Mansion, Circa 1886 is a fine dining restaurant that evokes the romance and old-world charm of historic downtown Charleston.

Visit circa1886.com

Key Findings

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

Performance Metrics

circa1886.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value2,670 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value1.04

2/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

circa1886.com

197 ms

circa1886.com

355 ms

gtm.js

69 ms

sbi-styles.min.css

30 ms

default.css

26 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 68% of them (94 requests) were addressed to the original Circa1886.com, 16% (22 requests) were made to Tcgms.net and 12% (17 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (947 ms) relates to the external source Tcgms.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 679.4 kB (11%)

Content Size

6.3 MB

After Optimization

5.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Circa1886.com main page is 6.3 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. Only a small number of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 319.2 kB

  • Original 369.3 kB
  • After minification 348.4 kB
  • After compression 50.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 319.2 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.8 MB
  • After minification 4.8 MB

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. Circa 1886 images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 192.2 kB

  • Original 714.1 kB
  • After minification 703.6 kB
  • After compression 521.9 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 192.2 kB or 27% of the original size.

CSS Optimization

-43%

Potential reduce by 167.9 kB

  • Original 394.5 kB
  • After minification 388.0 kB
  • After compression 226.5 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. Circa1886.com needs all CSS files to be minified and compressed as it can save up to 167.9 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (71%)

Requests Now

114

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

circa1886.com accessibility score

64

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[role] values are not valid

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

circa1886.com SEO score

82

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

Links do not have descriptive text

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

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 Circa1886.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 Circa1886.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 Circa 1886. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: