782 ms in total
12 ms
564 ms
206 ms
Visit brianhaynes.org now to see the best up-to-date Brian Haynes content and also check out these interesting facts you probably never knew about brianhaynes.org
Brian Haynes is a pastor, teacher, and writer whose passion is to restore people, families and churches.
Visit brianhaynes.orgWe analyzed Brianhaynes.org page load time and found that the first response time was 12 ms and then it took 770 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
brianhaynes.org performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value4.4 s
40/100
25%
Value3.1 s
93/100
10%
Value10 ms
100/100
30%
Value0.276
44/100
15%
Value4.6 s
81/100
10%
12 ms
25 ms
119 ms
152 ms
144 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Brianhaynes.org, 18% (7 requests) were made to Fonts.wp.com and 15% (6 requests) were made to S2.wp.com. The less responsive or slowest element that took the longest time to load (280 ms) relates to the external source R-login.wordpress.com.
Page size can be reduced by 101.0 kB (28%)
363.0 kB
262.0 kB
In fact, the total size of Brianhaynes.org main page is 363.0 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. 50% of websites need less resources to load. Images take 164.4 kB which makes up the majority of the site volume.
Potential reduce by 77.1 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 77.1 kB or 78% of the original size.
Potential reduce by 23.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. Obviously, Brian Haynes needs image optimization as it can save up to 23.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 223 B
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 469 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. Brianhaynes.org has all CSS files already compressed.
Number of requests can be reduced by 19 (66%)
29
10
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brian Haynes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
brianhaynes.org
12 ms
brianhaynes.org
25 ms
webfont.js
119 ms
jetpack-likes.css
152 ms
style.css
144 ms
148 ms
156 ms
148 ms
block-editor.css
164 ms
158 ms
css
185 ms
153 ms
156 ms
152 ms
hovercards.min.js
160 ms
wpgroho.js
148 ms
160 ms
w.js
182 ms
css
82 ms
global-print.css
24 ms
cropped-letterheadlogo-1.jpg
133 ms
platform.js
25 ms
g.gif
241 ms
remote-login.php
280 ms
cropped-brianhaynes_teaching-1.jpg
221 ms
cropped-letterheadlogo-1.jpg
179 ms
g.gif
229 ms
g.gif
233 ms
tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvLFG6rXmq.woff
162 ms
tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvy1a6rXmq.woff
162 ms
Genericons.svg
40 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
3 ms
u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7ilwQ.woff
160 ms
pxiEyp8kv8JHgFVrJJnedA.woff
160 ms
pxiByp8kv8JHgFVrLCz7Z1JlEw.woff
159 ms
pxiGyp8kv8JHgFVrJJLufntG.woff
168 ms
font
169 ms
actionbar.css
3 ms
actionbar.js
3 ms
brianhaynes.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.
brianhaynes.org 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
brianhaynes.org 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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brianhaynes.org 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 Brianhaynes.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.
brianhaynes.org
Open Graph data is detected on the main page of Brian Haynes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: