Tools & Wizards About Us
pendercountync.gov screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

pendercountync.gov

Pender County, NC | Official Website

Page Load Speed

6.5 sec in total

First Response

103 ms

Resources Loaded

4.1 sec

Page Rendered

2.3 sec

pendercountync.gov screenshot

About Website

Visit pendercountync.gov now to see the best up-to-date Pender County NC content for United States and also check out these interesting facts you probably never knew about pendercountync.gov

COVID-19 Data for NC & Pender County Pender County Health Department is now offering the following COVID-19 Vaccines: Moderna Pfizer Johnson & Johnson Note:  Pfizer-BioNTech and Moderna COVID-19 vacci...

Visit pendercountync.gov

Key Findings

We analyzed Pendercountync.gov page load time and found that the first response time was 103 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

pendercountync.gov performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value2,530 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.209

59/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

pendercountync.gov

103 ms

www.pendercountync.gov

789 ms

js

203 ms

wp-emoji-release.min.js

165 ms

formidableforms1.css

311 ms

Our browser made a total of 136 requests to load all elements on the main page. We found that 78% of them (106 requests) were addressed to the original Pendercountync.gov, 9% (12 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (41%)

Content Size

4.0 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pendercountync.gov main page is 4.0 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 142.1 kB

  • Original 174.6 kB
  • After minification 163.3 kB
  • After compression 32.6 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 142.1 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.8 MB
  • After minification 1.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. Pender County NC images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 340.7 kB

  • Original 593.9 kB
  • After minification 584.4 kB
  • After compression 253.2 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 340.7 kB or 57% of the original size.

CSS Optimization

-85%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 1.3 MB
  • After compression 210.1 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. Pendercountync.gov needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 85% of the original size.

Requests Breakdown

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

Requests Now

116

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pendercountync.gov

pendercountync.gov

103 ms

www.pendercountync.gov

www.pendercountync.gov

789 ms

js

js

203 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

165 ms

formidableforms1.css

formidableforms1.css

311 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

307 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

309 ms

style.min.css

style.min.css

350 ms

styles.css

styles.css

303 ms

style.css

style.css

313 ms

ditty.css

ditty.css

380 ms

all.css

all.css

375 ms

style.min.css

style.min.css

321 ms

events_manager.css

events_manager.css

354 ms

style.css

style.css

388 ms

toolbar.css

toolbar.css

318 ms

main.css

main.css

358 ms

simple-banner.css

simple-banner.css

358 ms

font-awesome.min.css

font-awesome.min.css

382 ms

a11y-toolbar.css

a11y-toolbar.css

386 ms

a11y.css

a11y.css

423 ms

a11y-fontsize.css

a11y-fontsize.css

424 ms

wpa-style.css

wpa-style.css

426 ms

style.css

style.css

452 ms

style.css

style.css

426 ms

cff-style.min.css

cff-style.min.css

406 ms

font-awesome.min.css

font-awesome.min.css

166 ms

default.min.css

default.min.css

409 ms

js_composer.min.css

js_composer.min.css

574 ms

button-styles.css

button-styles.css

414 ms

staff-list.css

staff-list.css

526 ms

wpmu-ui.3.min.css

wpmu-ui.3.min.css

489 ms

animate.3.min.css

animate.3.min.css

531 ms

message-ticker.js

message-ticker.js

523 ms

jquery.min.js

jquery.min.js

524 ms

jquery-migrate.min.js

jquery-migrate.min.js

529 ms

frontend-gtag.min.js

frontend-gtag.min.js

538 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

564 ms

wp-polyfill.min.js

wp-polyfill.min.js

564 ms

core.min.js

core.min.js

564 ms

element.js

element.js

182 ms

api.js

api.js

158 ms

css

css

182 ms

mouse.min.js

mouse.min.js

561 ms

analytics.js

analytics.js

79 ms

sortable.min.js

sortable.min.js

443 ms

collect

collect

29 ms

datepicker.min.js

datepicker.min.js

295 ms

menu.min.js

menu.min.js

294 ms

dom-ready.min.js

dom-ready.min.js

291 ms

hooks.min.js

hooks.min.js

430 ms

i18n.min.js

i18n.min.js

429 ms

a11y.min.js

a11y.min.js

424 ms

autocomplete.min.js

autocomplete.min.js

425 ms

collect

collect

37 ms

resizable.min.js

resizable.min.js

397 ms

draggable.min.js

draggable.min.js

397 ms

controlgroup.min.js

controlgroup.min.js

394 ms

checkboxradio.min.js

checkboxradio.min.js

390 ms

button.min.js

button.min.js

375 ms

dialog.min.js

dialog.min.js

370 ms

events-manager.js

events-manager.js

370 ms

simple-banner.js

simple-banner.js

341 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

333 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

331 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

331 ms

vimeo.min.js

vimeo.min.js

327 ms

index.js

index.js

324 ms

swiped-events.min.js

swiped-events.min.js

320 ms

dashicons.min.css

dashicons.min.css

339 ms

font-awesome.min.css

font-awesome.min.css

256 ms

imagesloaded.min.js

imagesloaded.min.js

227 ms

effect.min.js

effect.min.js

227 ms

ditty-news-ticker.min.js

ditty-news-ticker.min.js

223 ms

gallery.min.js

gallery.min.js

222 ms

scripts.js

scripts.js

514 ms

detectmobilebrowser.js

detectmobilebrowser.js

510 ms

mystickymenu.min.js

mystickymenu.min.js

512 ms

wpa-toolbar.js

wpa-toolbar.js

487 ms

a11y.js

a11y.js

487 ms

longdesc.button.js

longdesc.button.js

862 ms

current-menu-item.js

current-menu-item.js

862 ms

masonry.min.js

masonry.min.js

907 ms

jquery.masonry.min.js

jquery.masonry.min.js

861 ms

third-party.js

third-party.js

912 ms

library.min.js

library.min.js

766 ms

scripts.min.js

scripts.min.js

766 ms

cff-scripts.min.js

cff-scripts.min.js

765 ms

index.js

index.js

768 ms

wp-accessibility.js

wp-accessibility.js

768 ms

wpmu-ui.3.min.js

wpmu-ui.3.min.js

788 ms

public.min.js

public.min.js

780 ms

js_composer_front.min.js

js_composer_front.min.js

780 ms

New_Pender_Logo_NoBG_whiteshadow-e1499103731920.png

New_Pender_Logo_NoBG_whiteshadow-e1499103731920.png

463 ms

DSC_0083.jpg

DSC_0083.jpg

462 ms

SeaGrassCropped.jpg

SeaGrassCropped.jpg

463 ms

SCPierUnder.png

SCPierUnder.png

465 ms

DSC_0036.jpg

DSC_0036.jpg

495 ms

DJI_0016-2-2-e1497539187277.jpg

DJI_0016-2-2-e1497539187277.jpg

460 ms

DSC_0208.jpg

DSC_0208.jpg

463 ms

TopsailInlet.png

TopsailInlet.png

490 ms

CornRows.png

CornRows.png

490 ms

Moores-Creek-1-1024x683.jpg

Moores-Creek-1-1024x683.jpg

463 ms

css.png

css.png

489 ms

Faster-Pender.png

Faster-Pender.png

490 ms

CodeRed.jpg

CodeRed.jpg

491 ms

Website-Feedback.png

Website-Feedback.png

490 ms

sand2.png

sand2.png

503 ms

Large-Seal-nobg-e1485969218595.png

Large-Seal-nobg-e1485969218595.png

502 ms

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7nsDc.ttf

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7nsDc.ttf

749 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkids18E.ttf

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkids18E.ttf

752 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZYokSds18E.ttf

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZYokSds18E.ttf

752 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZY4lCds18E.ttf

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZY4lCds18E.ttf

750 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSds18E.ttf

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSds18E.ttf

751 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZklyds18E.ttf

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZklyds18E.ttf

896 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

908 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

908 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

908 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

908 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

1015 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

1062 ms

townpress.ttf

townpress.ttf

733 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

723 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

726 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

737 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

735 ms

analytics.js

analytics.js

1048 ms

a11y.woff

a11y.woff

661 ms

recaptcha__en.js

recaptcha__en.js

828 ms

flags.png

flags.png

373 ms

js

js

571 ms

478 ms

gen_204

gen_204

243 ms

common.js

common.js

25 ms

util.js

util.js

11 ms

geocoder.js

geocoder.js

200 ms

Accessibility Review

pendercountync.gov accessibility score

89

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pendercountync.gov best practices score

83

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

High

Browser errors were logged to the console

SEO Factors

pendercountync.gov SEO score

77

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 Pendercountync.gov 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 Pendercountync.gov 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

pendercountync.gov

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