1.6 sec in total
43 ms
804 ms
725 ms
Click here to check amazing Nc Gov content for United States. Otherwise, check out these important facts you probably never knew about ncgov.com
North Carolina's Official Website, featuring information about government services, updates, and guides to exploring and enjoying our state.
Visit ncgov.comWe analyzed Ncgov.com page load time and found that the first response time was 43 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
ncgov.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value7.4 s
4/100
25%
Value4.0 s
81/100
10%
Value480 ms
60/100
30%
Value0.063
97/100
15%
Value9.2 s
32/100
10%
43 ms
77 ms
69 ms
128 ms
20 ms
Our browser made a total of 187 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ncgov.com, 83% (155 requests) were made to Nc.gov and 5% (9 requests) were made to Files.nc.gov. The less responsive or slowest element that took the longest time to load (261 ms) relates to the external source Fonts.googleapis.com.
Page size can be reduced by 136.4 kB (5%)
2.8 MB
2.7 MB
In fact, the total size of Ncgov.com main page is 2.8 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. 65% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 55.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 7.8 kB, which is 11% 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 55.8 kB or 80% of the original size.
Potential reduce by 52.5 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. Nc Gov images are well optimized though.
Potential reduce by 11.0 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.0 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. Ncgov.com needs all CSS files to be minified and compressed as it can save up to 17.0 kB or 23% of the original size.
Number of requests can be reduced by 164 (91%)
180
16
The browser has sent 180 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nc Gov. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 74 to 1 for JavaScripts and from 92 to 1 for CSS and as a result speed up the page load time.
ncgov.com
43 ms
www.nc.gov
77 ms
js
69 ms
gtm.js
128 ms
core.css
20 ms
controlgroup.css
26 ms
checkboxradio.css
32 ms
resizable.css
24 ms
button.css
30 ms
dialog.css
30 ms
ajax-progress.module.css
32 ms
align.module.css
30 ms
autocomplete-loading.module.css
35 ms
fieldgroup.module.css
32 ms
container-inline.module.css
33 ms
clearfix.module.css
42 ms
details.module.css
32 ms
hidden.module.css
35 ms
item-list.module.css
36 ms
js.module.css
41 ms
nowrap.module.css
34 ms
position-container.module.css
36 ms
progress.module.css
39 ms
reset-appearance.module.css
38 ms
resize.module.css
38 ms
sticky-header.module.css
37 ms
system-status-counter.css
41 ms
system-status-report-counters.css
40 ms
system-status-report-general-info.css
43 ms
tabledrag.module.css
39 ms
tablesort.module.css
54 ms
tree-child.module.css
41 ms
video_card.css
53 ms
spotlight.css
42 ms
carousel.css
44 ms
contact.css
42 ms
section.css
46 ms
tabs_accordion.css
46 ms
cta_card.css
47 ms
bootstrap.min.css
94 ms
monsido-script.js
153 ms
bootstrap.bundle.min.js
152 ms
core.css
45 ms
tooltip.css
44 ms
nc_map.css
38 ms
quick_links.css
38 ms
stat_card.css
60 ms
profile_card.css
58 ms
event_card.css
57 ms
article_card.css
58 ms
ckeditor5.dialog.fix.css
57 ms
filter.caption.css
72 ms
filter.caption.css
88 ms
theme.css
84 ms
theme.css
85 ms
paragraphs.unpublished.css
82 ms
carousel.css
81 ms
variables.css
125 ms
user.css
124 ms
progress.css
121 ms
node.css
123 ms
affix.css
121 ms
book.css
121 ms
contextual.css
164 ms
feed-icon.css
164 ms
field.css
162 ms
header.css
161 ms
help.css
160 ms
icons.css
161 ms
css
169 ms
css2
261 ms
bootstrap-icons.css
118 ms
image-button.css
170 ms
item-list.css
167 ms
list-group.css
168 ms
media.css
166 ms
page.css
166 ms
search-form.css
164 ms
shortcut.css
241 ms
sidebar.css
217 ms
site-footer.css
214 ms
skip-link.css
219 ms
table.css
218 ms
tabledrag.css
215 ms
tableselect.css
218 ms
tablesort-indicator.css
193 ms
ui.widget.css
194 ms
tabs.css
194 ms
toolbar.css
195 ms
js
123 ms
analytics.js
177 ms
vertical-tabs.css
196 ms
views.css
182 ms
webform.css
166 ms
ui-dialog.css
167 ms
style.css
166 ms
icons.css
173 ms
nc_theme.css
179 ms
jquery.min.js
135 ms
once.min.js
142 ms
drupalSettingsLoader.js
136 ms
drupal.js
138 ms
drupal.init.js
140 ms
debounce.js
138 ms
version-min.js
100 ms
data-min.js
100 ms
disable-selection-min.js
100 ms
form-min.js
100 ms
jquery-patch-min.js
114 ms
scroll-parent-min.js
112 ms
unique-id-min.js
104 ms
focusable-min.js
104 ms
ie-min.js
106 ms
keycode-min.js
104 ms
plugin-min.js
105 ms
safe-active-element-min.js
87 ms
safe-blur-min.js
88 ms
widget-min.js
86 ms
labels-min.js
87 ms
controlgroup-min.js
85 ms
form-reset-mixin-min.js
82 ms
mouse-min.js
161 ms
checkboxradio-min.js
159 ms
draggable-min.js
159 ms
resizable-min.js
157 ms
button-min.js
157 ms
dialog-min.js
155 ms
version-min.js
164 ms
keycode-min.js
158 ms
position-min.js
157 ms
unique-id-min.js
153 ms
widget-min.js
153 ms
tooltip-min.js
152 ms
index.umd.min.js
172 ms
tua-bsl.umd.min.js
170 ms
google_analytics.js
169 ms
barrio.js
166 ms
global.js
167 ms
nc.search.js
165 ms
nc.analytics.js
190 ms
spotlight.js
189 ms
carousel.js
189 ms
tabs_accordion.js
187 ms
ncgov_250X75_2.png
154 ms
nc-map.js
177 ms
user_testing.jpg
178 ms
nc_real_id.jpg
190 ms
hiking%20family-GettyImages-1254013331.jpg
234 ms
hurricane-eye-2.jpg
235 ms
nc_flag.jpg
217 ms
nclogo.png
208 ms
stat_card.js
175 ms
progress.js
186 ms
loadjs.min.js
186 ms
announce.js
186 ms
message.js
210 ms
ajax.js
184 ms
collect
96 ms
dropdown.js
138 ms
displace.js
148 ms
jquery.tabbable.shim.js
174 ms
position.js
173 ms
dialog.js
169 ms
dialog.position.js
170 ms
dialog.jquery-ui.js
171 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
145 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
169 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
188 ms
bootstrap-icons.woff
106 ms
ckeditor5.dialog.fix.js
189 ms
nc_spring_2023.jpg
176 ms
about_band_bg.jpg
149 ms
dialog.ajax.js
117 ms
webform.drupal.dialog.js
117 ms
webform.dialog.js
115 ms
ncalerts.js
116 ms
portal-search.js
110 ms
nc.gtranslate.js
114 ms
search.svg
113 ms
collect
73 ms
9Bt73C1KxNDXMspQ1lPyU89-1h6ONRlW45G8WbcNcw.ttf
98 ms
print.css
6 ms
print.css
3 ms
tracking.monsido.com
80 ms
heatmaps.js
38 ms
mon-page-assist-loader.js
52 ms
eeawbdPSiJH5oAfVdjbhog.json
7 ms
ncgov.com accessibility score
ncgov.com 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
Page has valid source maps
ncgov.com 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 Ncgov.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 Ncgov.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.
ncgov.com
Open Graph data is detected on the main page of Nc Gov. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: