1.6 sec in total
88 ms
550 ms
918 ms
Click here to check amazing Duke Park content. Otherwise, check out these important facts you probably never knew about dukepark.org
The Duke Park Neighborhood Association in Durham, NC strives to improve the quality of life for all Duke Park residents through partnerships, community events, and direct action.
Visit dukepark.orgWe analyzed Dukepark.org page load time and found that the first response time was 88 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.
dukepark.org performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value5.3 s
21/100
25%
Value3.8 s
84/100
10%
Value470 ms
61/100
30%
Value0.029
100/100
15%
Value5.8 s
67/100
10%
88 ms
96 ms
90 ms
95 ms
101 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 93% of them (37 requests) were addressed to the original Dukepark.org, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (149 ms) belongs to the original domain Dukepark.org.
Page size can be reduced by 58.0 kB (8%)
728.4 kB
670.5 kB
In fact, the total size of Dukepark.org main page is 728.4 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. 35% of websites need less resources to load. Images take 559.6 kB which makes up the majority of the site volume.
Potential reduce by 31.4 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 4.5 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 31.4 kB or 75% of the original size.
Potential reduce by 8.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. Duke Park images are well optimized though.
Potential reduce by 18.2 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 18.2 kB or 16% of the original size.
Potential reduce by 191 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. Dukepark.org has all CSS files already compressed.
Number of requests can be reduced by 8 (22%)
37
29
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duke Park. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
dukepark.org
88 ms
www.dukepark.org
96 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
90 ms
css_r5D6EwZQWYo9X7jpieoDt1ZdcEvBWd5DAxv4HN-UTf0.css
95 ms
css_J8FLJ38YOi554yHAZUhoJQXbggNv_bE3Wg0JpYPgL6M.css
101 ms
css_zklSznxX8aI1K5fKtNHT4h82TWbtsMpYgz8UR7Mvmk8.css
102 ms
js_XexEZhbTmj1BHeajKr2rPfyR8Y68f4rm0Nv3Vj5_dSI.js
131 ms
js_FVhN18bbqzYEkTilvl31hOmd8NQtZUZya3wnwWYKd_Y.js
119 ms
js_YRhnKlf4CncQXuyTjjn-T2ynZ8hBCTVvxI3bqUxYqFE.js
109 ms
js_xl9HTiK_AeM7BXuygpHTWHT2hdLu-Qc8oPl5hN6IBOU.js
149 ms
analytics.js
88 ms
bg-dirt.jpg
64 ms
bg-top-skyline-hero.jpg
35 ms
bg-top.jpg
36 ms
hero-sign.png
64 ms
nav-full.jpg
34 ms
loader-cloud.gif
30 ms
bg-grass.png
48 ms
bg-paper-top.jpg
55 ms
bg-paper-bottom.jpg
54 ms
bg-paper.jpg
71 ms
home-photos.png
70 ms
new-duke-park-sign.jpg
71 ms
1617905610-45742465.jpg
88 ms
562169_3614911165143_1436972342_n%20%281%29.jpg
76 ms
tree-banding.jpg
86 ms
holiday-luminarias-1186432.jpg
88 ms
santa-claus-hat-1443996.jpg
94 ms
newsletter-header.gif
92 ms
BQP2016_DamItsthe80s_Logo.jpg
101 ms
play-1337317-1919x1081.jpg
131 ms
newsletter.jpg
58 ms
search.svg
106 ms
parade_end.jpg
131 ms
logo_swashbuckler.gif
39 ms
icon-facebook-white.png
40 ms
icon-youtube-white.png
45 ms
lobstertwo-bolditalic-webfont.woff
131 ms
collect
13 ms
js
68 ms
dukepark.org accessibility score
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
dukepark.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
Browser errors were logged to the console
dukepark.org 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dukepark.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 Dukepark.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.
dukepark.org
Open Graph description is not detected on the main page of Duke Park. 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: