6.1 sec in total
2.3 sec
3.6 sec
222 ms
Click here to check amazing Corrales Nm content for United States. Otherwise, check out these important facts you probably never knew about corrales-nm.org
Visit corrales-nm.orgWe analyzed Corrales-nm.org page load time and found that the first response time was 2.3 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
corrales-nm.org performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value3.5 s
63/100
25%
Value3.5 s
89/100
10%
Value340 ms
74/100
30%
Value0
100/100
15%
Value4.8 s
79/100
10%
2277 ms
141 ms
129 ms
135 ms
95 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 81% of them (96 requests) were addressed to the original Corrales-nm.org, 5% (6 requests) were made to Use.edgefonts.net and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Corrales-nm.org.
Page size can be reduced by 1.2 MB (60%)
2.1 MB
830.0 kB
In fact, the total size of Corrales-nm.org main page is 2.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. 75% 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. CSS take 832.2 kB which makes up the majority of the site volume.
Potential reduce by 47.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 47.3 kB or 81% of the original size.
Potential reduce by 21.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. Corrales Nm images are well optimized though.
Potential reduce by 497.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 497.6 kB or 72% of the original size.
Potential reduce by 680.6 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. Corrales-nm.org needs all CSS files to be minified and compressed as it can save up to 680.6 kB or 82% of the original size.
Number of requests can be reduced by 75 (74%)
102
27
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Corrales Nm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
corrales-nm.org
2277 ms
wp-emoji-release.min.js
141 ms
pfo_filter_styles.css
129 ms
pfo_rows_styles.css
135 ms
pfo-widget-style.css
95 ms
dashicons.min.css
198 ms
wunderground.css
133 ms
widget.min.css
152 ms
css
34 ms
awesome-weather.css
178 ms
css
61 ms
styles.css
188 ms
skins.css
184 ms
cff-style.css
225 ms
font-awesome.min.css
34 ms
events_manager.css
234 ms
bwg_frontend.css
229 ms
sumoselect.css
229 ms
font-awesome.css
236 ms
jquery.mCustomScrollbar.css
247 ms
tribe-events-full.min.css
270 ms
tribe-events-theme.min.css
275 ms
default.min.css
278 ms
general_foundicons.css
309 ms
social_foundicons.css
311 ms
otw_shortcode.css
370 ms
megamenu.css
355 ms
font-awesome.min.css
22 ms
css
41 ms
mb-button.css
331 ms
style.css
399 ms
shortcode.css
363 ms
cp_default.css
366 ms
mega_menu.css
375 ms
bootstrap.css
439 ms
font-awesome.css
410 ms
css
47 ms
jquery.js
457 ms
jquery-migrate.min.js
417 ms
core.min.js
419 ms
widget.min.js
455 ms
position.min.js
456 ms
lato.js
61 ms
layerslider.css
415 ms
wdstwitterwidget.css
390 ms
menu.min.js
364 ms
autocomplete.min.js
363 ms
widget.min.js
369 ms
alfie.weather.min.js
374 ms
alfie-weather.min.js
375 ms
mouse.min.js
359 ms
sortable.min.js
360 ms
datepicker.min.js
359 ms
resizable.min.js
365 ms
draggable.min.js
341 ms
button.min.js
344 ms
dialog.min.js
364 ms
events-manager.js
363 ms
bwg_frontend.js
355 ms
jquery.sumoselect.min.js
359 ms
jquery.mobile.js
342 ms
jquery.mCustomScrollbar.concat.min.js
344 ms
jquery.fullscreen-0.4.1.js
361 ms
bwg_gallery_box.js
343 ms
picturefill.min.js
334 ms
layerslider.kreaturamedia.jquery.js
382 ms
greensock.js
305 ms
layerslider.transitions.js
298 ms
cff-scripts.js
323 ms
bootstrap.js
330 ms
frontend_scripts.js
335 ms
social_slider_script.js
311 ms
social_slider_main.js
325 ms
wp-embed.min.js
323 ms
close.png
277 ms
loading.gif
293 ms
prev.png
290 ms
next.png
294 ms
corrales-nm.org
192 ms
tribe-events-full-mobile.min.css
54 ms
tribe-events-theme-mobile.min.css
114 ms
41e97300b00ecc625951fbde85496b3d_normal.jpeg
380 ms
villagebanner6.png
185 ms
nav-top.png
82 ms
blank.gif
82 ms
welcome-corrales.png
78 ms
villageseal3.png
185 ms
message-mayor.png
82 ms
mayor.jpg
154 ms
four-leaf-clover-md.png
184 ms
residents-button-300x98.png
184 ms
corrales_logo-300x71.jpg
184 ms
riogrande-png-150x150.png
184 ms
border-bg_2.png
344 ms
ajax-loader.gif
346 ms
footer-top.jpg
344 ms
footer-bg.jpg
343 ms
fb_hr.png
344 ms
twitter_hr.png
344 ms
ue9uW6QDDcendc_pfl2efjO7HfQqJVx8VwqOlBv2KVCffHhqgsMdeMJ6Mk6fwyBuSh90ZAs1ZAZzd1sDOco8i265.woff
40 ms
TbRnCvmv10kN4jqsC7ozB1xhu0ChdCYwwfqflZNieyIffOHqgsMdeMJ6Mk6fwyBuSh90ZAs1ZAZzd1sDOco8i26s.woff
143 ms
Dopb7dy69kTeo1u_6R20avo4zIzonPViIQHRwuvwcuJffHkqgsMdeMJ6Mk6fwyBuSh90ZAs1ZAZzd1sDOco8i26I.woff
336 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
35 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
35 ms
BTu4SsVveqk58cdYjlaM9g.ttf
39 ms
vDvcuXwZxUMLuTfuLrSLpA.ttf
34 ms
Ql7HFTxZUFk-LlNQSjjVhJQCCp4LAxcbn30BRk25dyGffOeqgsMdeMJ6Mk6fwyBuSh90ZAs1ZAZzd1sDOco8i26Y.woff
335 ms
zpv3sOKAbMf4wff105oLjw.ttf
35 ms
5pEc4QKTMA2oB4Hi9NkS4w.ttf
34 ms
city-government
306 ms
twitter-icon.png
242 ms
riogrande-png.png
242 ms
fontawesome-webfont.woff
224 ms
fontawesome-webfont.woff
13 ms
fontawesome-webfont.woff
223 ms
fontawesome-webfont.woff
13 ms
p.gif
230 ms
skin.css
91 ms
corrales-nm.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
corrales-nm.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
corrales-nm.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corrales-nm.org 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 Corrales-nm.org 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.
corrales-nm.org
Open Graph description is not detected on the main page of Corrales Nm. 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: