Tools & Wizards About Us
fayettevillenc.va.gov screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

fayettevillenc.va.gov

VA Fayetteville Coastal Health Care | Veterans Affairs

Page Load Speed

3.3 sec in total

First Response

530 ms

Resources Loaded

2.6 sec

Page Rendered

180 ms

fayettevillenc.va.gov screenshot

About Website

Click here to check amazing Fayetteville Nc VA content for United States. Otherwise, check out these important facts you probably never knew about fayettevillenc.va.gov

At VA Fayetteville Coastal health care, our health care teams are deeply experienced and guided by the needs of Veterans, their families, and caregivers. Find a health facility near you, and manage yo...

Visit fayettevillenc.va.gov

Key Findings

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

Performance Metrics

fayettevillenc.va.gov performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value2,510 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.278

44/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

fayettevillenc.va.gov

530 ms

fayetteville-coastal-health-care

380 ms

148 ms

polyfills.entry.js

484 ms

web-components.css

317 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fayettevillenc.va.gov, 44% (14 requests) were made to Prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com and 31% (10 requests) were made to S3-us-gov-west-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.0 kB (7%)

Content Size

1.0 MB

After Optimization

962.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fayettevillenc.va.gov main page is 1.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. 55% of websites need less resources to load. Javascripts take 689.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 67.1 kB

  • Original 82.0 kB
  • After minification 74.8 kB
  • After compression 14.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. 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 67.1 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 2.4 kB

  • Original 166.8 kB
  • After minification 164.4 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. Fayetteville Nc VA images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 117 B

  • Original 689.8 kB
  • After minification 689.8 kB
  • After compression 689.6 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

-3%

Potential reduce by 3.4 kB

  • Original 96.6 kB
  • After minification 96.5 kB
  • After compression 93.2 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. Fayettevillenc.va.gov has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (50%)

Requests Now

22

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fayettevillenc.va.gov

fayettevillenc.va.gov

530 ms

fayetteville-coastal-health-care

fayetteville-coastal-health-care

380 ms

148 ms

polyfills.entry.js

polyfills.entry.js

484 ms

web-components.css

web-components.css

317 ms

web-components.entry.js

web-components.entry.js

455 ms

style.css

style.css

451 ms

content-build.css

content-build.css

321 ms

static-pages.css

static-pages.css

353 ms

vendor.entry.js

vendor.entry.js

624 ms

static-pages.entry.js

static-pages.entry.js

1131 ms

Universal-Federated-Analytics-Min.js

Universal-Federated-Analytics-Min.js

23 ms

embed.js

embed.js

622 ms

gtm.js

gtm.js

274 ms

tiny-usa-flag.png

tiny-usa-flag.png

245 ms

icon-dot-gov.svg

icon-dot-gov.svg

245 ms

icon-https.svg

icon-https.svg

287 ms

arrow-right-white.svg

arrow-right-white.svg

359 ms

header-logo.png

header-logo.png

375 ms

FACEBOOK%20COVER.jpg

FACEBOOK%20COVER.jpg

499 ms

FayettevilleNC_480x330.jpg

FayettevilleNC_480x330.jpg

442 ms

TreniaPevia.JPG

TreniaPevia.JPG

477 ms

ambulance.JPG

ambulance.JPG

441 ms

sourcesanspro-bold-webfont.woff

sourcesanspro-bold-webfont.woff

216 ms

sourcesanspro-regular-webfont.woff

sourcesanspro-regular-webfont.woff

220 ms

sourcesanspro-light-webfont.woff

sourcesanspro-light-webfont.woff

217 ms

polyfills-dom.entry.js

polyfills-dom.entry.js

148 ms

polyfills-core-js.entry.js

polyfills-core-js.entry.js

472 ms

bitter-bold.ttf

bitter-bold.ttf

130 ms

bitter-regular.ttf

bitter-regular.ttf

118 ms

fa-solid-900.woff

fa-solid-900.woff

181 ms

fa-regular-400.woff

fa-regular-400.woff

129 ms

Accessibility Review

fayettevillenc.va.gov accessibility score

100

Accessibility Issues

Best Practices

fayettevillenc.va.gov best practices score

92

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

Page has valid source maps

SEO Factors

fayettevillenc.va.gov SEO score

99

Search Engine Optimization Advices

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 Fayettevillenc.va.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 Fayettevillenc.va.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

fayettevillenc.va.gov

Open Graph data is detected on the main page of Fayetteville Nc VA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: