6.6 sec in total
546 ms
3.4 sec
2.6 sec
Welcome to brianmayer.com homepage info - get ready to check Brian Mayer best content for United States right away, or after learning these important things about brianmayer.com
Visit brianmayer.comWe analyzed Brianmayer.com page load time and found that the first response time was 546 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
brianmayer.com performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value7.8 s
3/100
25%
Value9.0 s
15/100
10%
Value2,200 ms
6/100
30%
Value0.004
100/100
15%
Value16.0 s
6/100
10%
546 ms
25 ms
75 ms
58 ms
97 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 38% of them (29 requests) were addressed to the original Brianmayer.com, 16% (12 requests) were made to Facebook.com and 13% (10 requests) were made to Api-public.addthis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source D2jutb8bry7gi8.cloudfront.net.
Page size can be reduced by 1.4 MB (65%)
2.2 MB
759.2 kB
In fact, the total size of Brianmayer.com main page is 2.2 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. 70% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 208.5 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 208.5 kB or 76% of the original size.
Potential reduce by 75.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. Obviously, Brian Mayer needs image optimization as it can save up to 75.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.0 MB
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 1.0 MB or 75% of the original size.
Potential reduce by 80.9 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. Brianmayer.com needs all CSS files to be minified and compressed as it can save up to 80.9 kB or 82% of the original size.
Number of requests can be reduced by 27 (36%)
74
47
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brian Mayer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
brianmayer.com
546 ms
css
25 ms
style.css
75 ms
shortcodes.css
58 ms
font-awesome.min.css
97 ms
wzslider.css
57 ms
custom.css
99 ms
jquery.js
151 ms
jquery-migrate.min.js
98 ms
init.js
106 ms
bf882208
87 ms
wp-emoji-release.min.js
49 ms
addthis_widget.js
10 ms
output.css
28 ms
dropdown.js
25 ms
custom.js
27 ms
galleria.js
213 ms
wzslider.js
212 ms
wp-embed.min.js
212 ms
ajax-loader-sm.gif
1064 ms
analytics.js
131 ms
285010_4039728586683_332727940_n4.jpg
984 ms
ico-post.png
984 ms
date.png
983 ms
comments.png
984 ms
Screen-Shot-2015-07-04-at-9.07.42-AM-1024x371.png
987 ms
america-300x188.png
984 ms
BN-FU581_bkrvfo_FR_20141201135820-234x300.jpg
985 ms
2666578-300x255.jpg
988 ms
screenshot-1-169x300.png
989 ms
screenshot-2-169x300.png
987 ms
arrows.png
986 ms
wpzoom.png
988 ms
bebas.woff
918 ms
bf882208
186 ms
300lo.json
83 ms
all.js&version=v2.0
775 ms
widgets.js
92 ms
pinit00.png
29 ms
counter.5524cceca805eb4b9b2b.js
60 ms
collect
40 ms
sh.8e5f85691f9aaa082472a194.html
38 ms
shares.json
55 ms
shares.json
180 ms
shares.json
54 ms
shares.json
53 ms
shares.json
53 ms
shares.json
51 ms
shares.json
51 ms
shares.json
51 ms
shares.json
50 ms
shares.json
50 ms
layers.e5ea973510bf60b3db41.js
29 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
304 ms
jquery.dataTables.js
122 ms
jobs-widget.css
68 ms
jquery.dataTables.css
68 ms
sort_both.png
47 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
87 ms
127 ms
jot.html
28 ms
xd_arbiter.php
224 ms
xd_arbiter.php
427 ms
ping
71 ms
like.php
84 ms
like.php
117 ms
like.php
108 ms
like.php
121 ms
like.php
129 ms
qeKvIRsJabD.js
488 ms
LVx-xkvaJ0b.png
552 ms
like.php
106 ms
like.php
134 ms
like.php
148 ms
like.php
140 ms
like.php
149 ms
brianmayer.com 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
brianmayer.com 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
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
brianmayer.com 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
Image elements do not have [alt] attributes
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
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 Brianmayer.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 Brianmayer.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.
brianmayer.com
Open Graph description is not detected on the main page of Brian Mayer. 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: