14.9 sec in total
6 sec
8.1 sec
859 ms
Welcome to visitchapelhill.org homepage info - get ready to check Visit Chapel Hill best content for United States right away, or after learning these important things about visitchapelhill.org
The Chapel Hill & Orange County Community welcomes you! Visit us to experience some of the best dining, shopping, arts, sports and recreation North Carolina has to offer.
Visit visitchapelhill.orgWe analyzed Visitchapelhill.org page load time and found that the first response time was 6 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
visitchapelhill.org performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value21.3 s
0/100
25%
Value9.5 s
12/100
10%
Value1,130 ms
22/100
30%
Value0.931
3/100
15%
Value20.0 s
2/100
10%
5956 ms
484 ms
531 ms
208 ms
341 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 47% of them (34 requests) were addressed to the original Visitchapelhill.org, 8% (6 requests) were made to Google.com and 7% (5 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Visitchapelhill.org.
Page size can be reduced by 201.1 kB (8%)
2.6 MB
2.4 MB
In fact, the total size of Visitchapelhill.org main page is 2.6 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. 60% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 34.0 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 5.8 kB, which is 14% 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 34.0 kB or 80% of the original size.
Potential reduce by 148.0 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. Visit Chapel Hill images are well optimized though.
Potential reduce by 6.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 6.0 kB or 16% of the original size.
Potential reduce by 13.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. Visitchapelhill.org needs all CSS files to be minified and compressed as it can save up to 13.0 kB or 82% of the original size.
Number of requests can be reduced by 28 (45%)
62
34
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Visit Chapel Hill. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
visitchapelhill.org
5956 ms
bootstrap.min.js
484 ms
global.css
531 ms
photogallery.css
208 ms
promos.css
341 ms
Cleandesign_general.js
178 ms
liveperson.js
207 ms
uds7dkl.js
188 ms
instafeed.min.js,home.js
410 ms
all.js
19 ms
print.css
201 ms
cse.js
165 ms
tre
131 ms
tre
169 ms
activity;src=1889519;type=ta_ch972;cat=ta_ho488;ord=1959630592
130 ms
chocvb-slider-oldwell316.jpg
705 ms
chocvb-slider-diningatsouthernvillage316.JPG
557 ms
chocvb-slider-weaverstreet316.jpg
885 ms
chocvb-slider-Hillsborough316.JPG
871 ms
chocvb-slider-140west316.JPG
708 ms
Carrboro_Farmers_Market_570_by_379.jpg
573 ms
NCAA_Basketball_UNC_462_by_305.jpg
601 ms
Easter_Egg_Hunt_462_vy_305.jpg
869 ms
NC_Beer_Month_462_by_305.jpg
868 ms
FINAL_2016_OCVG_Cover64x64.jpg
874 ms
Accessible_icon_promo_64_x_64.jpg
874 ms
Park_on_the_Hill_Logo_Promo.jpg
876 ms
promo-thumb.jpg
890 ms
lgbt-flag.jpg
876 ms
secondary-nav-bg-1200.png
153 ms
2ndary-nav-divider.jpg
152 ms
glyphicons-halflings.png
151 ms
primary-nav-bg-1200.png
150 ms
experience-btn-back.png
151 ms
experience-btn.png
236 ms
logo.png
236 ms
content-bg-1200.png
246 ms
home-date-ribbon-lg.png
227 ms
cse.js
93 ms
iframe
34 ms
iframe
48 ms
cv_pixel.js
739 ms
fontawesome-webfont.woff
282 ms
iframe
26 ms
fbevents.js
9 ms
iframe
7 ms
ga.js
10 ms
500 ms
getuid
46 ms
__utm.gif
198 ms
jsapi
361 ms
cse.js
166 ms
recent
509 ms
collect
436 ms
prev.png
168 ms
next.png
166 ms
cse.js
164 ms
generic
137 ms
321 ms
xd_arbiter.php
96 ms
xd_arbiter.php
173 ms
default+en.css
59 ms
default.css
151 ms
default+en.I.js
149 ms
default.css
111 ms
12826089_1689096611349762_1969126259_n.jpg
203 ms
10518217_480526985488153_638357757_n.jpg
242 ms
10431772_1670458706539329_128262506_n.jpg
283 ms
12798013_1763031727243235_1240061594_n.jpg
325 ms
12819143_1127427697268462_1886065337_n.jpg
324 ms
mTag.js
186 ms
cv.php
83 ms
visitchapelhill.org accessibility score
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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
visitchapelhill.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
visitchapelhill.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Visitchapelhill.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Visitchapelhill.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.
visitchapelhill.org
Open Graph description is not detected on the main page of Visit Chapel Hill. 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: