1.8 sec in total
37 ms
882 ms
904 ms
Visit ncdcr.gov now to see the best up-to-date NC Dcr content for United States and also check out these interesting facts you probably never knew about ncdcr.gov
Visit ncdcr.govWe analyzed Ncdcr.gov page load time and found that the first response time was 37 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
ncdcr.gov performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value15.6 s
0/100
25%
Value4.2 s
78/100
10%
Value620 ms
48/100
30%
Value0.001
100/100
15%
Value11.4 s
19/100
10%
37 ms
193 ms
71 ms
132 ms
16 ms
Our browser made a total of 189 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ncdcr.gov, 84% (158 requests) were made to Dncr.nc.gov and 3% (6 requests) were made to Files.nc.gov. The less responsive or slowest element that took the longest time to load (373 ms) relates to the external source Files.nc.gov.
Page size can be reduced by 931.1 kB (15%)
6.2 MB
5.3 MB
In fact, the total size of Ncdcr.gov main page is 6.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.9 MB which makes up the majority of the site volume.
Potential reduce by 65.7 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 9.9 kB, which is 12% 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 65.7 kB or 81% of the original size.
Potential reduce by 836.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, NC Dcr needs image optimization as it can save up to 836.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 11.8 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.
Potential reduce by 17.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. Ncdcr.gov needs all CSS files to be minified and compressed as it can save up to 17.5 kB or 23% of the original size.
Number of requests can be reduced by 168 (93%)
180
12
The browser has sent 180 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NC Dcr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 78 to 1 for JavaScripts and from 92 to 1 for CSS and as a result speed up the page load time.
ncdcr.gov
37 ms
www.dncr.nc.gov
193 ms
js
71 ms
gtm.js
132 ms
core.css
16 ms
controlgroup.css
16 ms
checkboxradio.css
25 ms
resizable.css
24 ms
button.css
24 ms
dialog.css
24 ms
ajax-progress.module.css
25 ms
align.module.css
24 ms
autocomplete-loading.module.css
28 ms
fieldgroup.module.css
26 ms
container-inline.module.css
25 ms
clearfix.module.css
26 ms
details.module.css
28 ms
hidden.module.css
27 ms
item-list.module.css
28 ms
js.module.css
34 ms
nowrap.module.css
29 ms
position-container.module.css
30 ms
progress.module.css
30 ms
reset-appearance.module.css
33 ms
resize.module.css
32 ms
sticky-header.module.css
31 ms
system-status-counter.css
32 ms
system-status-report-counters.css
32 ms
system-status-report-general-info.css
36 ms
tabledrag.module.css
35 ms
tablesort.module.css
38 ms
tree-child.module.css
37 ms
video_card.css
33 ms
spotlight.css
35 ms
carousel.css
41 ms
contact.css
41 ms
section.css
40 ms
tabs_accordion.css
42 ms
cta_card.css
41 ms
bootstrap.min.css
51 ms
monsido-script.js
58 ms
bootstrap.bundle.min.js
56 ms
jquery.validate.min.js
90 ms
core.css
34 ms
tooltip.css
42 ms
nc_map.css
41 ms
quick_links.css
42 ms
stat_card.css
33 ms
profile_card.css
32 ms
event_card.css
33 ms
article_card.css
73 ms
ckeditor5.dialog.fix.css
76 ms
views.module.css
77 ms
theme.css
74 ms
theme.css
76 ms
paragraphs.unpublished.css
76 ms
carousel.css
99 ms
variables.css
98 ms
user.css
96 ms
progress.css
95 ms
node.css
97 ms
affix.css
96 ms
book.css
99 ms
contextual.css
96 ms
feed-icon.css
94 ms
field.css
97 ms
header.css
95 ms
help.css
95 ms
css
120 ms
css2
168 ms
bootstrap-icons.css
31 ms
icons.css
95 ms
image-button.css
96 ms
item-list.css
98 ms
list-group.css
93 ms
media.css
95 ms
page.css
96 ms
search-form.css
93 ms
shortcut.css
94 ms
sidebar.css
93 ms
site-footer.css
95 ms
skip-link.css
94 ms
table.css
96 ms
tabledrag.css
87 ms
tableselect.css
87 ms
tablesort-indicator.css
88 ms
ui.widget.css
89 ms
tabs.css
81 ms
toolbar.css
81 ms
vertical-tabs.css
47 ms
views.css
48 ms
webform.css
46 ms
ui-dialog.css
46 ms
style.css
47 ms
form.css
70 ms
icons.css
67 ms
ilm_theme.css
69 ms
jquery.min.js
71 ms
once.min.js
71 ms
drupalSettingsLoader.js
71 ms
drupal.js
71 ms
drupal.init.js
70 ms
debounce.js
70 ms
version-min.js
71 ms
data-min.js
70 ms
disable-selection-min.js
70 ms
form-min.js
70 ms
jquery-patch-min.js
70 ms
scroll-parent-min.js
111 ms
unique-id-min.js
110 ms
focusable-min.js
110 ms
ie-min.js
111 ms
keycode-min.js
113 ms
plugin-min.js
110 ms
safe-active-element-min.js
109 ms
safe-blur-min.js
109 ms
widget-min.js
110 ms
labels-min.js
111 ms
controlgroup-min.js
109 ms
form-reset-mixin-min.js
111 ms
mouse-min.js
110 ms
checkboxradio-min.js
110 ms
draggable-min.js
110 ms
resizable-min.js
112 ms
button-min.js
110 ms
dialog-min.js
110 ms
version-min.js
110 ms
keycode-min.js
110 ms
position-min.js
104 ms
unique-id-min.js
104 ms
js
159 ms
analytics.js
158 ms
widget-min.js
137 ms
tooltip-min.js
135 ms
index.umd.min.js
132 ms
tua-bsl.umd.min.js
131 ms
google_analytics.js
131 ms
barrio.js
130 ms
global.js
132 ms
nc.search.js
133 ms
nc.analytics.js
132 ms
spotlight.js
197 ms
carousel.js
197 ms
tabs_accordion.js
196 ms
nc-map.js
195 ms
dropdown.js
208 ms
DNCR%20Web%20Logo%201.png
211 ms
stat_card.js
156 ms
Carousel%20or%20Home%20Page%20Main%20Image%20with%20Search%20Box%20%284%29.png
254 ms
Article%20Card%20Image%20%284%29.png
256 ms
A250NC%201200x675%20Logo%20Graphic.png
373 ms
Library%20WeekArticle%20Card%20Library%20Week%402x.png
354 ms
MicrosoftTeams-image%20%2812%29.png
259 ms
progress.js
154 ms
loadjs.min.js
176 ms
announce.js
175 ms
message.js
173 ms
ajax.js
174 ms
displace.js
173 ms
jquery.tabbable.shim.js
174 ms
position.js
186 ms
dialog.js
181 ms
dialog.position.js
180 ms
dialog.jquery-ui.js
179 ms
ckeditor5.dialog.fix.js
178 ms
dialog.ajax.js
178 ms
webform.drupal.dialog.js
205 ms
webform.dialog.js
204 ms
cv.jquery.validate.js
202 ms
cv.jquery.ife.js
201 ms
ncalerts.js
188 ms
portal-search.js
200 ms
nc.gtranslate.js
202 ms
search.svg
202 ms
core.js
190 ms
star.gif
230 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
179 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
181 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
213 ms
bootstrap-icons.woff
100 ms
icomoon.woff
126 ms
collect
63 ms
collect
102 ms
print.css
41 ms
starV6.gif
56 ms
fbevents.js
29 ms
print.css
5 ms
tracking.monsido.com
41 ms
heatmaps.js
37 ms
ncdcr.gov accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
ARIA IDs are not unique
ncdcr.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ncdcr.gov SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ncdcr.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 Ncdcr.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.
ncdcr.gov
Open Graph description is not detected on the main page of NC Dcr. 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: