Tools & Wizards About Us
co.mecklenburg.nc.us screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

co.mecklenburg.nc.us

Home | Mecklenburg County Government

Page Load Speed

9 sec in total

First Response

455 ms

Resources Loaded

8.4 sec

Page Rendered

170 ms

co.mecklenburg.nc.us screenshot

About Website

Click here to check amazing Co Mecklenburg content for United States. Otherwise, check out these important facts you probably never knew about co.mecklenburg.nc.us

Visit co.mecklenburg.nc.us

Key Findings

We analyzed Co.mecklenburg.nc.us page load time and found that the first response time was 455 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

co.mecklenburg.nc.us performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value33.7 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.449

20/100

15%

TTI (Time to Interactive)

Value21.2 s

1/100

10%

Network Requests Diagram

co.mecklenburg.nc.us

455 ms

84 ms

SearchResults.aspx

829 ms

corev15-51C31438.themedcss

119 ms

searchv15-6159CCCD.themedcss

76 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Co.mecklenburg.nc.us, 78% (64 requests) were made to Charmeck.org and 5% (4 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (829 ms) relates to the external source Charmeck.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (66%)

Content Size

3.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Co.mecklenburg.nc.us main page is 3.1 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. 60% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 263.5 kB

  • Original 306.8 kB
  • After minification 287.4 kB
  • After compression 43.3 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 263.5 kB or 86% of the original size.

Image Optimization

-15%

Potential reduce by 62.6 kB

  • Original 411.8 kB
  • After minification 349.1 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. Obviously, Co Mecklenburg needs image optimization as it can save up to 62.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 1.4 MB

  • Original 1.9 MB
  • After minification 1.9 MB
  • After compression 570.7 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 1.4 MB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 388.3 kB

  • Original 468.9 kB
  • After minification 442.2 kB
  • After compression 80.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. Co.mecklenburg.nc.us needs all CSS files to be minified and compressed as it can save up to 388.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (73%)

Requests Now

75

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

co.mecklenburg.nc.us

co.mecklenburg.nc.us

455 ms

84 ms

SearchResults.aspx

SearchResults.aspx

829 ms

corev15-51C31438.themedcss

corev15-51C31438.themedcss

119 ms

searchv15-6159CCCD.themedcss

searchv15-6159CCCD.themedcss

76 ms

init.js

init.js

86 ms

fluentribbonui.js

fluentribbonui.js

54 ms

ScriptResource.axd

ScriptResource.axd

70 ms

blank.js

blank.js

69 ms

ScriptResource.axd

ScriptResource.axd

89 ms

sp.init.js

sp.init.js

103 ms

clientrenderer.js

clientrenderer.js

87 ms

ScriptResx.ashx

ScriptResx.ashx

106 ms

search.clientcontrols.js

search.clientcontrols.js

170 ms

search.cbs.js

search.cbs.js

169 ms

filter_default.js

filter_default.js

168 ms

filter_mcfiletype.js

filter_mcfiletype.js

182 ms

filter_mcdefault.js

filter_mcdefault.js

182 ms

control_mcrefinement.js

control_mcrefinement.js

186 ms

control_searchbox.js

control_searchbox.js

183 ms

item_commonitem_body.js

item_commonitem_body.js

183 ms

group_default.js

group_default.js

183 ms

item_default.js

item_default.js

183 ms

item_site.js

item_site.js

185 ms

item_word.js

item_word.js

183 ms

item_powerpoint.js

item_powerpoint.js

187 ms

item_person_compacthorizontal.js

item_person_compacthorizontal.js

189 ms

item_bestbet.js

item_bestbet.js

188 ms

item_webpage.js

item_webpage.js

190 ms

control_mcsearchresults.js

control_mcsearchresults.js

189 ms

item_mcitem.js

item_mcitem.js

192 ms

group_content.js

group_content.js

191 ms

control_mclist.js

control_mclist.js

193 ms

combined.min.css

combined.min.css

190 ms

libraries.min.js

libraries.min.js

253 ms

scripts.min.js

scripts.min.js

203 ms

masterpage-script.js

masterpage-script.js

202 ms

WebResource.axd

WebResource.axd

203 ms

element.js

element.js

49 ms

css

css

23 ms

favicon.ico

favicon.ico

30 ms

spcommon.png

spcommon.png

23 ms

WebResource.axd

WebResource.axd

27 ms

2015-naco-achievement-small.png

2015-naco-achievement-small.png

26 ms

analytics.js

analytics.js

27 ms

siteanalyze_advanced.js

siteanalyze_advanced.js

318 ms

background-header.png

background-header.png

84 ms

flags.png

flags.png

80 ms

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

79 ms

MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf

MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf

80 ms

translateelement.css

translateelement.css

105 ms

main.js

main.js

153 ms

collect

collect

17 ms

collect

collect

92 ms

sprites.png

sprites.png

229 ms

background-footer-posted.png

background-footer-posted.png

50 ms

background-footer-stay-posted.png

background-footer-stay-posted.png

50 ms

background-footer.png

background-footer.png

90 ms

wrapper.js

wrapper.js

178 ms

element_main.js

element_main.js

141 ms

customstrings.js

customstrings.js

113 ms

eventmodalwindow.html

eventmodalwindow.html

73 ms

pagemodalwindow.html

pagemodalwindow.html

152 ms

searchresultui-61174269.themedpng

searchresultui-61174269.themedpng

142 ms

image.aspx

image.aspx

258 ms

translate_24dp.png

translate_24dp.png

184 ms

l

l

151 ms

cleardot.gif

cleardot.gif

179 ms

searchresultui-61174269.themedpng

searchresultui-61174269.themedpng

59 ms

icxlsx.png

icxlsx.png

58 ms

icpdf.png

icpdf.png

57 ms

icpptx.png

icpptx.png

84 ms

generaldocument.png

generaldocument.png

56 ms

icdocx.png

icdocx.png

57 ms

logo-blue.png

logo-blue.png

83 ms

WopiFrame.aspx

WopiFrame.aspx

492 ms

WopiFrame.aspx

WopiFrame.aspx

497 ms

initstrings.js

initstrings.js

21 ms

strings.js

strings.js

27 ms

core.js

core.js

36 ms

corev15-51C31438.themedcss

corev15-51C31438.themedcss

33 ms

iFrame.html

iFrame.html

39 ms

Accessibility Review

co.mecklenburg.nc.us accessibility score

87

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

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

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

Best Practices

co.mecklenburg.nc.us best practices score

50

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

Displays images with incorrect aspect ratio

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

co.mecklenburg.nc.us SEO score

93

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Co.mecklenburg.nc.us can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Co.mecklenburg.nc.us 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

co.mecklenburg.nc.us

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