1.6 sec in total
114 ms
1.3 sec
208 ms
Welcome to brillman.net homepage info - get ready to check Brillman best content right away, or after learning these important things about brillman.net
Quality Antique Tractor & Automotive Electrical Parts | We sell wiring harnesses, battery cables, spark plug wires, tune-up parts, and so much more!
Visit brillman.netWe analyzed Brillman.net page load time and found that the first response time was 114 ms and then it took 1.5 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.
brillman.net performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value16.8 s
0/100
25%
Value9.1 s
14/100
10%
Value1,390 ms
16/100
30%
Value0.005
100/100
15%
Value16.1 s
6/100
10%
114 ms
40 ms
525 ms
117 ms
78 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Brillman.net, 99% (73 requests) were made to Brillman.com. The less responsive or slowest element that took the longest time to load (525 ms) relates to the external source Brillman.com.
Page size can be reduced by 196.5 kB (25%)
781.9 kB
585.4 kB
In fact, the total size of Brillman.net main page is 781.9 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. 60% of websites need less resources to load. Images take 550.1 kB which makes up the majority of the site volume.
Potential reduce by 189.7 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. This page needs HTML code to be minified as it can gain 50.7 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 189.7 kB or 83% of the original size.
Potential reduce by 6.8 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. Brillman images are well optimized though.
Potential reduce by 0 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.
Number of requests can be reduced by 44 (65%)
68
24
The browser has sent 68 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 45 to 1 for CSS and as a result speed up the page load time.
brillman.net
114 ms
www.brillman.com
40 ms
www.brillman.com
525 ms
brillman.com
117 ms
grid.css
78 ms
base.css
39 ms
layout.css
42 ms
blog.css
70 ms
postslider.css
69 ms
buttons.css
32 ms
comments.css
52 ms
slideshow.css
65 ms
gallery.css
83 ms
grid_row.css
73 ms
heading.css
88 ms
hr.css
113 ms
image.css
87 ms
notification.css
107 ms
catalogue.css
97 ms
promobox.css
112 ms
slideshow_layerslider.css
113 ms
social_share.css
120 ms
tabs.css
118 ms
team.css
148 ms
toggles.css
137 ms
video.css
142 ms
layerslider.css
136 ms
shortcodes.css
149 ms
woocommerce-mod.css
143 ms
style.min.css
164 ms
topbar_style.css
193 ms
style.css
167 ms
dashicons.min.css
174 ms
algolia-satellite.min.css
173 ms
style-instant-search.css
194 ms
wc-avatax-frontend.min.css
216 ms
avia-snippet-fold-unfold.css
187 ms
magnific-popup.css
193 ms
avia-snippet-lightbox.css
184 ms
avia-snippet-widget.css
186 ms
brillman.css
184 ms
custom.css
178 ms
style.css
198 ms
sv-wc-payment-gateway-payment-form.min.css
164 ms
style.css
167 ms
awdr_style.css
190 ms
gravity-mod.css
174 ms
post-20718.css
170 ms
wc-blocks.css
162 ms
rocket-loader.min.js
152 ms
slide1.jpg
293 ms
redarrow.png
284 ms
slide2.jpg
272 ms
slide3.jpg
271 ms
B1055-007-1-web-B-450x450.jpg
271 ms
B1024-072-1-web-450x450.jpg
269 ms
b1001-004_web-2-450x450.jpg
265 ms
Placeholder-Product-Image-450x450.jpg
260 ms
B1070-014-1-web-450x450.jpg
245 ms
b1024-011_web-450x450.jpg
249 ms
B4007-042-1-Web-450x450.jpg
241 ms
B1024-019-1-web-450x450.jpg
239 ms
B4113-005-1-web-450x450.jpg
235 ms
B2026-019-1-web-450x450.jpg
233 ms
B2026-018-1-web-450x450.jpg
218 ms
B2026-017-1-web-450x450.jpg
212 ms
B2026-016-web-450x450.jpg
212 ms
8138-06-36x36.jpg
210 ms
pertronix-36x36.jpg
211 ms
loading-light.gif
125 ms
main.js
14 ms
entypo-fontello.woff
50 ms
gearedslab-bold-webfont.woff
41 ms
jquery.min.js
29 ms
brillman.net 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
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
Links do not have a discernible name
brillman.net 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
Missing source maps for large first-party JavaScript
brillman.net 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 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.net 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.net 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.net
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: