Tools & Wizards About Us
charlottesgotablog.com screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

charlottesgotablog.com

Charlotte Blog for Locals & Visitors | Charlotte's got a lot

Page Load Speed

4.3 sec in total

First Response

31 ms

Resources Loaded

4.1 sec

Page Rendered

215 ms

charlottesgotablog.com screenshot

About Website

Welcome to charlottesgotablog.com homepage info - get ready to check Charlotte S Got A Blog best content right away, or after learning these important things about charlottesgotablog.com

New to Charlotte or want to get reacquainted with our rapidly growing city? Stay on top of the latest events, openings and more with our local guide blog.

Visit charlottesgotablog.com

Key Findings

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

Performance Metrics

charlottesgotablog.com performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value21.1 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value2,980 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.463

19/100

15%

TTI (Time to Interactive)

Value24.4 s

0/100

10%

Network Requests Diagram

charlottesgotablog.com

31 ms

charlottesgotablog.com

28 ms

3092 ms

marvel.js

93 ms

sox6fel.css

60 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Charlottesgotablog.com, 32% (12 requests) were made to Use.typekit.net and 24% (9 requests) were made to Charlottesgotalot.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Charlottesgotalot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.3 kB (21%)

Content Size

374.2 kB

After Optimization

296.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 64.7 kB

  • Original 77.5 kB
  • After minification 56.4 kB
  • After compression 12.8 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. This page needs HTML code to be minified as it can gain 21.0 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 64.7 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.0 kB
  • After minification 2.0 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. Charlotte S Got A Blog images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.0 kB

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

CSS Optimization

-16%

Potential reduce by 11.6 kB

  • Original 74.3 kB
  • After minification 74.3 kB
  • After compression 62.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. Charlottesgotablog.com needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (48%)

Requests Now

21

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

charlottesgotablog.com

charlottesgotablog.com

31 ms

charlottesgotablog.com

charlottesgotablog.com

28 ms

3092 ms

marvel.js

marvel.js

93 ms

sox6fel.css

sox6fel.css

60 ms

app.css

app.css

72 ms

polyfills.js

polyfills.js

66 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

68 ms

carousels.js

carousels.js

66 ms

web-animations.min.js

web-animations.min.js

67 ms

app.js

app.js

427 ms

api.js

api.js

74 ms

pixel

pixel

39 ms

fbevents.js

fbevents.js

19 ms

p.css

p.css

60 ms

pixel

pixel

54 ms

match-result

match-result

6 ms

gtm.js

gtm.js

493 ms

gtm.js

gtm.js

603 ms

icons.svg

icons.svg

232 ms

charlotte-logo.png

charlotte-logo.png

229 ms

lines.svg

lines.svg

149 ms

lines-grey.svg

lines-grey.svg

230 ms

d

d

136 ms

d

d

216 ms

d

d

276 ms

d

d

351 ms

d

d

276 ms

d

d

276 ms

d

d

276 ms

d

d

350 ms

d

d

384 ms

d

d

384 ms

d

d

384 ms

recaptcha__en.js

recaptcha__en.js

317 ms

analytics

analytics

60 ms

analytics

analytics

50 ms

Accessibility Review

charlottesgotablog.com accessibility score

84

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-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

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

charlottesgotablog.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Missing source maps for large first-party JavaScript

SEO Factors

charlottesgotablog.com SEO score

75

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

High

Image elements do not have [alt] attributes

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

charlottesgotablog.com

Open Graph data is detected on the main page of Charlotte S Got A Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: