7.7 sec in total
31 ms
6.1 sec
1.6 sec
Welcome to blog.durham-nc.com homepage info - get ready to check Blog Durham Nc best content for United States right away, or after learning these important things about blog.durham-nc.com
Everything you need to know about events and things to do in Durham, NC, so you can explore like a local.
Visit blog.durham-nc.comWe analyzed Blog.durham-nc.com page load time and found that the first response time was 31 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
blog.durham-nc.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value20.5 s
0/100
25%
Value16.2 s
0/100
10%
Value17,320 ms
0/100
30%
Value0
100/100
15%
Value25.9 s
0/100
10%
31 ms
43 ms
764 ms
88 ms
165 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Blog.durham-nc.com, 5% (4 requests) were made to Connect.facebook.net and 5% (4 requests) were made to Match.adsrvr.org. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source 11271714.fls.doubleclick.net.
Page size can be reduced by 134.9 kB (17%)
780.6 kB
645.6 kB
In fact, the total size of Blog.durham-nc.com main page is 780.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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 514.5 kB which makes up the majority of the site volume.
Potential reduce by 130.6 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 130.6 kB or 78% of the original size.
Potential reduce by 2.2 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. Blog Durham Nc images are well optimized though.
Potential reduce by 1.4 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 781 B
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. Blog.durham-nc.com has all CSS files already compressed.
Number of requests can be reduced by 42 (71%)
59
17
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Durham Nc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and as a result speed up the page load time.
blog.discoverdurham.com
31 ms
blog.discoverdurham.com
43 ms
764 ms
foundation.js
88 ms
gtm.js
165 ms
weather-icon.js
108 ms
2295944.js
465 ms
cookieconsent.min.css
474 ms
cookieconsent.min.js
756 ms
sprite.svg
63 ms
sprite-eb.svg
84 ms
DMAP-Seal_190523_200343_fbf07c8e35bf04de56a3b7291e11b12b.png
97 ms
main.js
216 ms
site-search.js
216 ms
skycons.js
394 ms
analytics.js
760 ms
activity;xsp=4328459;ord=1;num=
2233 ms
conversion_async.js
1533 ms
core.js
1499 ms
insight.min.js
2191 ms
fbevents.js
1485 ms
2295944.js
2175 ms
mms.js
2175 ms
up.js
2255 ms
15632
2646 ms
js
280 ms
2236 ms
styles.min.css
400 ms
activityi;src=11271714;type=retar0;cat=disco0;ord=8598361401679;gtm=2wg9s0;auiddc=830420012.1664760266;~oref=https%3A%2F%2Fwww.discoverdurham.com%2Fblog%2F
2649 ms
main-nav.js
444 ms
fit-vids.js
430 ms
h-scroller.js
425 ms
page-scroll.js
425 ms
owl.carousel.js
1208 ms
videoPlayer.js
1207 ms
directories.js
1207 ms
leadflows.js
2376 ms
2295944.js
2376 ms
fb.js
2374 ms
a11y-dialog.js
1194 ms
BEVR178_Cocoa-Cinnamon_DiscoverDurham-1_96e32fd9db58534047002805bd7e22a3.jpg
1181 ms
IMG_9666_96e32fd9db58534047002805bd7e22a3.jpg
1181 ms
top-angle.svg
1601 ms
btm-white-angle-bg.svg
1602 ms
collect
1073 ms
collect
2116 ms
collect
1202 ms
IBMPlexSans-Light.woff
1074 ms
IBMPlexSans-Thin.woff
1075 ms
IBMPlexSans-Text.woff
1077 ms
IBMPlexSans.woff
1072 ms
IBMPlexSans-Medium.woff
1679 ms
IBMPlexSans-SemiBold.woff
1679 ms
IBMPlexSans-Bold.woff
1678 ms
IBMPlexSerif-Medium.woff
1696 ms
IBMPlexSerif.woff
1696 ms
IBMPlexSerif-Light.woff
1688 ms
IBMPlexSerif-ExtraLight.woff
2076 ms
IBMPlexSerif-Thin.woff
2067 ms
IBMPlexSerif-SemiBold.woff
2066 ms
IBMPlexSerif-Bold.woff
2152 ms
IBMPlexSans-Italic.woff
2295 ms
IBMPlexSans-MediumItalic.woff
2151 ms
IBMPlexSans-LightItalic.woff
2421 ms
IBMPlexSans-ExtraLightItalic.woff
2422 ms
IBMPlexSans-ThinItalic.woff
2420 ms
IBMPlexSans-SemiBoldItalic.woff
2424 ms
IBMPlexSans-BoldItalic.woff
2429 ms
DPAC009_DPAC-Durham-Performing-Arts-Center_DPAC-1_96e32fd9db58534047002805bd7e22a3.jpg
2323 ms
1802 ms
main.3a217bc7.js
439 ms
a11y-option-dropdown.js
1783 ms
identity.js
244 ms
1239637283175478
863 ms
PARK095_Durham-Belt-Line_DiscoverDurham_b342343a8b504e8f5d0251cd3697e416.jpg
1872 ms
0ce47a2a00256d71c8a6484.js
435 ms
src=11271714;type=retar0;cat=disco0;ord=8598361401679;gtm=2wg9s0;auiddc=830420012.1664760266;~oref=https%3A%2F%2Fwww.discoverdurham.com%2Fblog%2F
1112 ms
1333156440170020
397 ms
ga-audiences
351 ms
generic
495 ms
insights
458 ms
191 ms
generic
221 ms
generic
24 ms
generic
34 ms
19 ms
src=9537974;type=invmedia;cat=avldu0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;ord=1
17 ms
blog.durham-nc.com 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 have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
blog.durham-nc.com 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
Page has valid source maps
blog.durham-nc.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.durham-nc.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 Blog.durham-nc.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.
blog.durham-nc.com
Open Graph data is detected on the main page of Blog Durham Nc. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: