2.5 sec in total
32 ms
2.2 sec
334 ms
Welcome to blog.discoverdurham.com homepage info - get ready to check Blog Discover Durham best content for United States right away, or after learning these important things about blog.discoverdurham.com
Everything you need to know about events and things to do in Durham, NC, so you can explore like a local.
Visit blog.discoverdurham.comWe analyzed Blog.discoverdurham.com page load time and found that the first response time was 32 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
blog.discoverdurham.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value15.0 s
0/100
25%
Value5.7 s
52/100
10%
Value2,440 ms
5/100
30%
Value0
100/100
15%
Value14.4 s
9/100
10%
32 ms
35 ms
654 ms
17 ms
117 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Blog.discoverdurham.com, 51% (46 requests) were made to Discoverdurham.com and 9% (8 requests) were made to Match.adsrvr.org. The less responsive or slowest element that took the longest time to load (695 ms) relates to the external source Serve.uberads.com.
Page size can be reduced by 150.0 kB (15%)
1.0 MB
857.4 kB
In fact, the total size of Blog.discoverdurham.com main page is 1.0 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. 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 641.4 kB which makes up the majority of the site volume.
Potential reduce by 138.2 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 138.2 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 Discover Durham images are well optimized though.
Potential reduce by 8.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 838 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.discoverdurham.com has all CSS files already compressed.
Number of requests can be reduced by 41 (69%)
59
18
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Discover Durham. 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
32 ms
blog.discoverdurham.com
35 ms
654 ms
foundation.js
17 ms
j.php
117 ms
gtm.js
117 ms
weather-icon.js
24 ms
2295944.js
206 ms
cookieconsent.min.css
187 ms
cookieconsent.min.js
195 ms
sprite.svg
22 ms
sprite-eb.svg
35 ms
DMAP-Seal_190523_200343_fbf07c8e35bf04de56a3b7291e11b12b.png
37 ms
main.js
25 ms
site-search.js
32 ms
skycons.js
76 ms
main-nav.js
48 ms
fit-vids.js
50 ms
h-scroller.js
51 ms
page-scroll.js
49 ms
owl.carousel.js
58 ms
videoPlayer.js
59 ms
directories.js
59 ms
BLTO130_Blacktoberfest-2022_DiscoverDurham_96e32fd9db58534047002805bd7e22a3.jpg
17 ms
WEDS015_Rachele-Lawrence-Engagements-Highlights_LibbyMcGowan_96e32fd9db58534047002805bd7e22a3.jpg
17 ms
PG58_LODF30_21c-Museum-Hotel_ChrisCooper2015_96e32fd9db58534047002805bd7e22a3.jpg
15 ms
styles.min.css
91 ms
a11y-option-dropdown.js
76 ms
PARK095_Durham-Belt-Line_DiscoverDurham_276caa0c85efc2df0ada644ec9f84be0.jpg
78 ms
a11y-dialog.js
68 ms
js
123 ms
js
279 ms
analytics.js
396 ms
activity;xsp=4328459;ord=1;num=
616 ms
451 ms
core.js
445 ms
insight.min.js
489 ms
fbevents.js
435 ms
2295944.js
477 ms
mms.js
432 ms
15632
695 ms
up_loader.1.1.0.js
588 ms
events.js
588 ms
470 ms
top-angle.svg
230 ms
btm-white-angle-bg.svg
236 ms
IBMPlexSerif.woff
277 ms
IBMPlexSerif-Medium.woff
224 ms
IBMPlexSerif-Light.woff
232 ms
IBMPlexSerif-ExtraLight.woff
230 ms
IBMPlexSerif-Thin.woff
275 ms
IBMPlexSerif-SemiBold.woff
385 ms
IBMPlexSerif-Bold.woff
448 ms
IBMPlexSans-Light.woff
437 ms
IBMPlexSans-Thin.woff
405 ms
IBMPlexSans-Text.woff
447 ms
IBMPlexSans.woff
404 ms
IBMPlexSans-Medium.woff
528 ms
IBMPlexSans-SemiBold.woff
524 ms
IBMPlexSans-Bold.woff
496 ms
IBMPlexSans-Italic.woff
602 ms
IBMPlexSans-MediumItalic.woff
601 ms
IBMPlexSans-LightItalic.woff
600 ms
IBMPlexSans-ExtraLightItalic.woff
634 ms
IBMPlexSans-ThinItalic.woff
634 ms
IBMPlexSans-SemiBoldItalic.woff
633 ms
IBMPlexSans-BoldItalic.woff
662 ms
banner.js
568 ms
fb.js
525 ms
leadflows.js
568 ms
collect
174 ms
collect
310 ms
collect
198 ms
v2
328 ms
432 ms
0ce47a2a00256d71c8a6484.js
155 ms
events.js
390 ms
v2
333 ms
js
136 ms
ga-audiences
147 ms
generic
35 ms
generic
33 ms
saq_pxl
10 ms
li_sync
53 ms
generic
5 ms
generic
4 ms
appnexus
6 ms
rubicon
7 ms
rubicon
4 ms
src=9537974;type=invmedia;cat=avldu0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;ord=1
77 ms
generic
3 ms
blog.discoverdurham.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.discoverdurham.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.discoverdurham.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.discoverdurham.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.discoverdurham.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.discoverdurham.com
Open Graph data is detected on the main page of Blog Discover Durham. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: