1.9 sec in total
225 ms
1.4 sec
218 ms
Visit brianbrammer.com now to see the best up-to-date Brianbrammer content and also check out these interesting facts you probably never knew about brianbrammer.com
Visit brianbrammer.comWe analyzed Brianbrammer.com page load time and found that the first response time was 225 ms and then it took 1.7 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.
brianbrammer.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value3.6 s
60/100
25%
Value3.0 s
94/100
10%
Value200 ms
89/100
30%
Value0.007
100/100
15%
Value3.8 s
89/100
10%
225 ms
19 ms
178 ms
25 ms
281 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Brianbrammer.com, 73% (30 requests) were made to Use.typekit.net and 7% (3 requests) were made to Static.squarespace.com. The less responsive or slowest element that took the longest time to load (333 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 194.4 kB (27%)
725.7 kB
531.4 kB
In fact, the total size of Brianbrammer.com main page is 725.7 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. 55% of websites need less resources to load. Images take 506.6 kB which makes up the majority of the site volume.
Potential reduce by 194.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. 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 194.4 kB or 89% of the original size.
Potential reduce by 0 B
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. Brianbrammer images are well optimized though.
Number of requests can be reduced by 3 (33%)
9
6
The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brianbrammer. 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 CSS and as a result speed up the page load time.
www.brianbrammer.com
225 ms
slide-normalize.css
19 ms
Q9PLjcOG4t9JLE_O3fCqDg7rL3c_wWapcuEC2cL4Zobfez62f4e6pUJ6wRMU5QwXFmvuFAjDFQic5A9XjRgyweJa52quFABqF2q-dWiaikoKSc8ydc4kjAulZWJ0jhNlOe4k-AB0j14ydAu8SKoRdhXCdeNRjAUGdaFXOe4k-AB0OA4kjAulZWJ0SaBujW48Sagyjh90jhNlOfG0j14TjAtlj14ydAu8SKoDSWmyScmDSeBRZPoRdhXKIeZkZA81-YblShB0Sku3ScvKfAZuiYmkjPu3ifJeZWmkdagyH6qJqeqbMg62JMJ7fbKs-sMMeMX6MKG4fwTmIMMjgfMfH6qJRAqbMg65JMJ7fbKP-sMMeM96MKG4f4FTIMMj2kMfH6qJ8eqbMg6eJMJ7fbKm-sMMegM6MKG4fJoTIMMjgkMfH6qJRhqbMg6sJMJ7fbKA-sMMeMq6MKG4f4iTIMMjIkMfH6qJy89bMs62JMJ7fbK2msMgeMX6MKG4fJsmIMIjgfMfH6qJym9bMs65JMJ7fbRxmgMgeM96MKG4fJgmIMIj2kMfH6qJ6m9bMs6YJMJ7fbKfmsMgegI6MKG4fJimIMIjffMfH6qJKB9bMs6PJMJ7fbKTpsMfeMw6MKGHf55eMsMfeMX6MKG4fHToIMJjgfMfH6GJoJjgIMJj2KMfH6qJ7YqbMy6YJMJ7f6R8y6IbMy6sJMHbML2Ra7vB.js
178 ms
css
25 ms
www.brianbrammer.com
281 ms
common-c2cb21af65f6d18bb4c6-min.js
57 ms
slides-af1cd6579bfad73dd00f-min.js
45 ms
slides-7081d88649c1a997d76ac110831078d9-min.css
25 ms
dsc_00861.jpg
231 ms
RecordHit
267 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
8 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
10 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
32 ms
oqcL6jGD7ETFpC_PQ04C4uTpWjsjhn_yy0n7rh7szgGffHdQggMdeMJ6Mk6f5MX.woff
51 ms
2sQzLF7j-yBPxyKWJZR8Wy3iMNIn3vN1vR6PYBfKp06ffHLQggMdeMJ6Mk6f5Mt.woff
71 ms
mFs4uEa4B6Yx28DlaGy1rGhFHuduSKC4uMfVAS3VV_9ffHRQggMdeMJ6Mk6f5gI.woff
153 ms
u781yIpXDCOSpYJxIJk_-cYCV-VP3Q43BF0SygDHXLCffHVQggMdeMJ6Mk6f5Mw.woff
176 ms
r7Iz4u3HMws5Xo3B3dyRu5uLPTUNvNHqm3yywbkcRD9ffHQQggMdeMJ6Mk6f5Mb.woff
195 ms
7AjHx0jCL4iOLnItT8L4RkbMJs5AFlMt78cPweoWoA3ffHWQggMdeMJ6Mk6f5MS.woff
193 ms
qmaKzj-INAJVvl17sVU9bx2-BZOq1_ck83YAuT8XAGqffFcAggMdeMJ6Mk6f5MX.woff
194 ms
bKCDtsrKI1m3xDTTnZygIiz6ATVMDQZTWxuBj0qlWOCffF0AggMdeMJ6Mk6f5Mt.woff
194 ms
vINZ9u5kDR_gbw03sZBCWSXQdPKBzfhGg_uTsJrym6CffFhAggMdeMJ6Mk6f5Mv.woff
195 ms
MpjIzDVwm-mIOENwNIZEiHd5n_1bS-eHlgPAebTnYBjffFrAggMdeMJ6Mk6f5gM.woff
216 ms
0zrX4aOtAlzJBY9mfN3wR7i5fNHHdqCUqMjJs1cY2xSff5eAggMdeMJ6Mk6f5gI.woff
216 ms
YrhtQ-0pAikdzUFNamiHbbpl88FGa67TyjAb456HM-Jff55AggMdeMJ6Mk6f5gw.woff
217 ms
2rLS_N3GGI8WfQ2-DvjwJEWJ7z6VX7kJt_io66sHfFtffFKAggMdeMJ6Mk6f5Mw.woff
217 ms
xh_HFQE_qiw2ZOCXpF45Zy2mZedkNlAawcJiDVV9LRJffF7AggMdeMJ6Mk6f5Mb.woff
217 ms
5DHgtgBjUCiHkhLJ7KhZALvJHXXc0-_vkht-ysoil4vffFkAggMdeMJ6Mk6f5M9.woff
215 ms
EyRWEy9ydsJENU0MwD_atQd6kLc_Y9Q3TSPFqbiqKo9ffFEAggMdeMJ6Mk6f5Mj.woff
240 ms
CEH2DrwgjeDUdOMRehdELQOVrnM8ZVTg1FIMcxLsDdMff5fAggMdeMJ6Mk6f5MS.woff
241 ms
MuBiA0fDINwGm5MqXSK9aIEx18uz6NHHmEAYBynEWdwff5HAggMdeMJ6Mk6f5Mq.woff
251 ms
bexmsjP20_UPDeXPFOfLutg86l877t44zL2HOeMXOqvff45gggMdeMJ6Mk6f5MX.woff
285 ms
djPNnCog0DV7H8xXQSfioQVjP7GkjZ55jPVilrqa9rCff4AgggMdeMJ6Mk6f5Mt.woff
269 ms
f9-JbLXx1xvXV69HvfxiyN7kB8ayJyOooYH5a-6cd7Mff4fgggMdeMJ6Mk6f5Mv.woff
271 ms
i21rBvJcr32iTQViG3qkeG_l_lTJI_1ibBSgOrmOBJGff4HgggMdeMJ6Mk6f5gI.woff
284 ms
uJ3lCaKEUKjGR3wc4ntRZihgGeWir6A4LrqkZzbpUYtff4KgggMdeMJ6Mk6f5gJ.woff
296 ms
kpP3Y-bCmjenQmqlpxGQpOkEwd6liPe4LTQf3HlmaK3ff4-gggMdeMJ6Mk6f5Mw.woff
325 ms
D6C_3jl_duovMTYfXgF96e6IMzQ8P_KQ0OP4ntVF0O6ff5WcggMdeMJ6Mk6f5Mb.woff
333 ms
fQC4fLvcdy9ptPpW2hq2TIICB0oHmWBg-oWcpLsRjG9ffJrgggMdeMJ6Mk6f5M9.woff
332 ms
kRNvijMdG0wdT0Fhl_0UGJcnAqbGjvKWlRd4qLuTqx6ff4egggMdeMJ6Mk6f5MS.woff
306 ms
QBuuSY3hQclM1xGlS_IqOk2DsAdcHSzPechf_QqV-G3ff4pgggMdeMJ6Mk6f5M6.woff
332 ms
brianbrammer.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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
brianbrammer.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
brianbrammer.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Brianbrammer.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 Brianbrammer.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.
brianbrammer.com
Open Graph description is not detected on the main page of Brianbrammer. 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: