1.9 sec in total
33 ms
1.6 sec
316 ms
Click here to check amazing Doug Dawson content. Otherwise, check out these important facts you probably never knew about doug-dawson.com
Visit doug-dawson.comWe analyzed Doug-dawson.com page load time and found that the first response time was 33 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
doug-dawson.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value10.6 s
0/100
25%
Value11.6 s
5/100
10%
Value8,350 ms
0/100
30%
Value0.399
25/100
15%
Value32.4 s
0/100
10%
33 ms
36 ms
139 ms
23 ms
76 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Doug-dawson.com, 43% (23 requests) were made to Dfs.nm.com and 13% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (956 ms) relates to the external source Mediahandler.broadridgeadvisor.com.
Page size can be reduced by 199.6 kB (6%)
3.1 MB
2.9 MB
In fact, the total size of Doug-dawson.com main page is 3.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. 85% 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. Javascripts take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 35.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 35.3 kB or 68% of the original size.
Potential reduce by 19.3 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. Doug Dawson images are well optimized though.
Potential reduce by 130.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. This website has mostly compressed JavaScripts.
Potential reduce by 14.3 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. Doug-dawson.com needs all CSS files to be minified and compressed as it can save up to 14.3 kB or 11% of the original size.
Number of requests can be reduced by 28 (67%)
42
14
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doug Dawson. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
doug-dawson.com
33 ms
doug-dawson.com
36 ms
dfs.nm.com
139 ms
launch-16ba86374f36-staging.min.js
23 ms
plugins.css
76 ms
Bootstrap-Icon.css
119 ms
theme-pcg.css
155 ms
dfs-team-profiles.css
61 ms
boostrap-jquery.bundle.js
154 ms
osano.js
357 ms
plugins.js
150 ms
jquery.validation.js
124 ms
main.js
198 ms
submitHandler.js
151 ms
theme-pcg.js
151 ms
ec-site-public.js
230 ms
ec-site-encryption.js
200 ms
global.js
200 ms
NM.js
229 ms
gtm.js
50 ms
js
60 ms
analytics.js
82 ms
collect
12 ms
62e9c822-238a-47f7-7bdb-f282048e7468.png
74 ms
PCG-logo-blue.png
89 ms
houston-business-journal-award.png
956 ms
livljWXG6sk
185 ms
player.flipsnack.com
74 ms
place
592 ms
downtown-background.jpg
574 ms
PCG-Blue.png
440 ms
GuardianSans-Regular.woff
179 ms
GuardianSans-Medium.woff
874 ms
GuardianSans-Light.woff
440 ms
GuardianSans-Bold.woff
260 ms
Tandelle-Regular.woff
390 ms
reader.gz.js
70 ms
handleUnsupportedBrowsers.gz.js
6 ms
Roboto-Regular.ttf
105 ms
Roboto-Medium.ttf
110 ms
Roboto-Bold.ttf
106 ms
iframe_api
37 ms
www-widgetapi.js
39 ms
www-player.css
41 ms
www-embed-player.js
59 ms
base.js
99 ms
ad_status.js
161 ms
cOmNekhtB6CR5q7D3-nraypsfm6DjXXigRslOSdWWYU.js
87 ms
embed.js
40 ms
js
148 ms
id
30 ms
Create
130 ms
GenerateIT
13 ms
doug-dawson.com accessibility score
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
doug-dawson.com 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 Doug-dawson.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 Doug-dawson.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.
doug-dawson.com
Open Graph description is not detected on the main page of Doug Dawson. 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: