1.2 sec in total
55 ms
896 ms
268 ms
Visit brillman.com now to see the best up-to-date Brillman content for United States and also check out these interesting facts you probably never knew about brillman.com
Quality Antique Tractor & Automotive Electrical Parts | We sell wiring harnesses, battery cables, spark plug wires, tune-up parts, and so much more!
Visit brillman.comWe analyzed Brillman.com page load time and found that the first response time was 55 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
brillman.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value15.2 s
0/100
25%
Value7.4 s
28/100
10%
Value2,010 ms
7/100
30%
Value0.002
100/100
15%
Value14.2 s
9/100
10%
55 ms
72 ms
32 ms
43 ms
45 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 94% of them (119 requests) were addressed to the original Brillman.com, 3% (4 requests) were made to Use.fontawesome.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (149 ms) belongs to the original domain Brillman.com.
Page size can be reduced by 162.3 kB (24%)
678.8 kB
516.5 kB
In fact, the total size of Brillman.com main page is 678.8 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. 65% of websites need less resources to load. Images take 458.2 kB which makes up the majority of the site volume.
Potential reduce by 161.8 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 161.8 kB or 77% 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. Brillman images are well optimized though.
Potential reduce by 402 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 61 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. Brillman.com has all CSS files already compressed.
Number of requests can be reduced by 99 (83%)
120
21
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brillman. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 45 to 1 for CSS and as a result speed up the page load time.
brillman.com
55 ms
brillman.com
72 ms
grid.css
32 ms
base.css
43 ms
layout.css
45 ms
blog.css
32 ms
postslider.css
55 ms
buttons.css
41 ms
comments.css
52 ms
slideshow.css
52 ms
gallery.css
66 ms
grid_row.css
68 ms
heading.css
64 ms
hr.css
71 ms
image.css
68 ms
notification.css
69 ms
catalogue.css
78 ms
promobox.css
81 ms
slideshow_layerslider.css
79 ms
social_share.css
83 ms
tabs.css
82 ms
team.css
84 ms
toggles.css
95 ms
video.css
93 ms
layerslider.css
96 ms
shortcodes.css
103 ms
woocommerce-mod.css
105 ms
style.min.css
99 ms
topbar_style.css
109 ms
style.css
116 ms
dashicons.min.css
112 ms
wc-avatax-frontend.min.css
110 ms
avia-snippet-fold-unfold.css
113 ms
magnific-popup.css
124 ms
avia-snippet-lightbox.css
128 ms
avia-snippet-widget.css
125 ms
21d8aa5dda.js
62 ms
js
88 ms
brillman.css
126 ms
custom.css
104 ms
style.css
114 ms
sv-wc-payment-gateway-payment-form.min.css
104 ms
search-forms.css
100 ms
awdr_style.css
101 ms
gravity-mod.css
99 ms
post-20718.css
99 ms
wc-blocks.css
106 ms
jquery.min.js
97 ms
jquery-migrate.min.js
108 ms
hooks.min.js
105 ms
mw-qbo-desktop-public.js
108 ms
tpbr_front.min.js
105 ms
js.cookie.min.js
107 ms
cart-fragments.min.js
101 ms
jquery.blockUI.min.js
101 ms
add-to-cart.min.js
100 ms
woocommerce.min.js
98 ms
avia-js.js
97 ms
avia-compat.js
99 ms
wpm-public.p1.min.js
104 ms
dismissible-wp-notices.js
118 ms
waypoints.js
110 ms
avia.js
98 ms
shortcodes.js
97 ms
gallery.js
92 ms
notification.js
100 ms
slideshow.js
103 ms
slideshow_layerslider.js
105 ms
tabs.js
102 ms
toggles.js
110 ms
slideshow-video.js
149 ms
video.js
104 ms
woocommerce-mod.js
100 ms
i18n.min.js
104 ms
main.js
102 ms
sourcebuster.min.js
100 ms
order-attribution.min.js
100 ms
variation-images-frontend.min.js
100 ms
site_main.js
105 ms
awdr-dynamic-price.js
102 ms
wc-avatax-frontend.min.js
111 ms
ada-edits.js
103 ms
avia-snippet-hamburger-menu.js
106 ms
avia-snippet-parallax.js
96 ms
avia-snippet-fold-unfold.js
92 ms
jquery.magnific-popup.js
100 ms
avia-snippet-lightbox.js
99 ms
avia-snippet-megamenu.js
100 ms
avia-snippet-footer-effects.js
102 ms
avia-snippet-widget.js
104 ms
jquery.payment.min.js
106 ms
sv-wc-payment-gateway-payment-form.min.js
113 ms
wc-authorize-net-aim.min.js
109 ms
awdr_pro.js
112 ms
avia_google_maps_front.js
111 ms
ioh03vqcfd
41 ms
21d8aa5dda.css
101 ms
hoverIntent.min.js
98 ms
maxmegamenu.js
100 ms
layerslider.utils.js
111 ms
layerslider.kreaturamedia.jquery.js
112 ms
layerslider.transitions.js
100 ms
clarity.js
14 ms
font-awesome-css.min.css
14 ms
slide1.jpg
68 ms
redarrow.png
63 ms
slide2.jpg
64 ms
slide3.jpg
65 ms
B1030-001-1-web-450x450.jpg
62 ms
B1057-001-1-Web-450x450.jpg
62 ms
Placeholder-Product-Image-450x450.jpg
65 ms
B1024-091-1-web-450x450.jpg
68 ms
B1000-006-1-web-450x450.jpg
66 ms
1007-039_web-450x450.jpg
67 ms
B9016-090-1-web-450x450.jpg
68 ms
B9014-017-1-web-450x450.jpg
69 ms
B9021-015-1-web-A-450x450.jpg
70 ms
B9021-014-1-web-450x450.jpg
70 ms
B9021-013-1-web-450x450.jpg
71 ms
B9038-027-1-web-450x450.jpg
71 ms
8138-06-36x36.jpg
72 ms
pertronix-36x36.jpg
72 ms
entypo-fontello.woff
43 ms
fontawesome-webfont.woff
23 ms
gearedslab-bold-webfont.woff
71 ms
loading-light.gif
17 ms
js
50 ms
brillman.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
brillman.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
brillman.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Brillman.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 Brillman.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.
brillman.com
Open Graph data is detected on the main page of Brillman. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: