10.4 sec in total
170 ms
4.9 sec
5.3 sec
Click here to check amazing Brian Dunning content for United States. Otherwise, check out these important facts you probably never knew about briandunning.com
FileMaker Pro and Lasso tips & tricks, downloads and courseware.
Visit briandunning.comWe analyzed Briandunning.com page load time and found that the first response time was 170 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
briandunning.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value7.1 s
5/100
25%
Value2.8 s
96/100
10%
Value60 ms
100/100
30%
Value0.008
100/100
15%
Value3.9 s
89/100
10%
170 ms
399 ms
170 ms
59 ms
340 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 97% of them (75 requests) were addressed to the original Briandunning.com, 1% (1 request) were made to Js-agent.newrelic.com and 1% (1 request) were made to Bam.nr-data.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Briandunning.com.
Page size can be reduced by 47.2 kB (3%)
1.4 MB
1.3 MB
In fact, the total size of Briandunning.com main page is 1.4 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 16.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 16.3 kB or 74% of the original size.
Potential reduce by 27.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. Brian Dunning images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.7 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. Briandunning.com needs all CSS files to be minified and compressed as it can save up to 2.7 kB or 84% of the original size.
Number of requests can be reduced by 14 (19%)
75
61
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brian Dunning. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
briandunning.com
170 ms
www.briandunning.com
399 ms
rollovers.js
170 ms
forms_val.js
59 ms
styles.css
340 ms
menu_1.jpg
643 ms
about_off.jpg
595 ms
menu_2.jpg
625 ms
productsdownloads_off.jpg
653 ms
customfunctions_off.jpg
670 ms
webviewerexamples_off.jpg
608 ms
consulting_off.jpg
637 ms
training_off.jpg
653 ms
books_off.jpg
653 ms
articles_off.jpg
653 ms
errorreference_off.jpg
797 ms
menu_3.jpg
618 ms
webtools_off.jpg
510 ms
filemakertools_off.jpg
472 ms
menu_4.jpg
618 ms
personalpages_off.jpg
599 ms
videos_off.jpg
1113 ms
adventures_off.jpg
1111 ms
links_off.jpg
1112 ms
menu_5.jpg
1185 ms
bottom.gif
1150 ms
shopping_cart.gif
1150 ms
syl_cover.png
1363 ms
quicklinks_off.gif
1050 ms
barcodebasics_off.gif
1049 ms
boardroom_off.gif
861 ms
calendarsnap_off.gif
1049 ms
cardvalidator_off.gif
1049 ms
cdmlmasterclass_off.gif
1023 ms
chartmakerpro_off.gif
1023 ms
dopewars_off.gif
1024 ms
easyencryption_off.gif
1023 ms
lassomasterclass_off.gif
1003 ms
progressbars_off.gif
1292 ms
simon_off.gif
1068 ms
weblets_off.gif
1292 ms
zipcodesfm_off.gif
1291 ms
award.jpg
1261 ms
chrome-logo.jpg
1260 ms
nr-1044.min.js
876 ms
about_on.jpg
346 ms
contact_on.jpg
345 ms
productsdownloads_on.jpg
318 ms
customfunctions_on.jpg
814 ms
consulting_on.jpg
815 ms
training_on.jpg
813 ms
books_on.jpg
814 ms
articles_on.jpg
813 ms
errorreference_on.jpg
813 ms
webtools_on.jpg
1149 ms
filemakertools_on.jpg
1148 ms
personalpages_on.jpg
1147 ms
videos_on.jpg
1147 ms
adventures_on.jpg
1149 ms
links_on.jpg
1146 ms
quicklinks_on.gif
1371 ms
boardroom_on.gif
1148 ms
cardvalidator_on.gif
1372 ms
cdmlmasterclass_on.gif
1373 ms
chartmakerpro_on.gif
1372 ms
dopewars_on.gif
1371 ms
lassomasterclass_on.gif
1422 ms
simon_on.gif
1331 ms
webletcharts_on.gif
1330 ms
webletchat_on.gif
1356 ms
webletcontacts_on.gif
1356 ms
webletshopping_on.gif
1356 ms
webletzipcodes_on.gif
1524 ms
zipcodesfm_on.gif
1523 ms
easyencryption_on.gif
1523 ms
barcodebasics_on.gif
1524 ms
5b07c0c3c7
595 ms
briandunning.com accessibility score
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
briandunning.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
briandunning.com SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Briandunning.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Briandunning.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.
briandunning.com
Open Graph description is not detected on the main page of Brian Dunning. 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: