1.8 sec in total
282 ms
1.1 sec
425 ms
Visit imaginebrick.com now to see the best up-to-date Imagine Brick content and also check out these interesting facts you probably never knew about imaginebrick.com
Providing Renovation, Repairs and Specialty Brickwork and Masonry Services in Charlotte, NC - since 2002. Let us create your outdoor kitchen, firepit or fireplace; add natural stone features, paver br...
Visit imaginebrick.comWe analyzed Imaginebrick.com page load time and found that the first response time was 282 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.
imaginebrick.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value19.0 s
0/100
25%
Value4.7 s
69/100
10%
Value1,240 ms
19/100
30%
Value0.01
100/100
15%
Value7.3 s
50/100
10%
282 ms
24 ms
47 ms
76 ms
65 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 91% of them (61 requests) were addressed to the original Imaginebrick.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (282 ms) belongs to the original domain Imaginebrick.com.
Page size can be reduced by 258.7 kB (4%)
6.4 MB
6.1 MB
In fact, the total size of Imaginebrick.com main page is 6.4 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. Images take 5.8 MB which makes up the majority of the site volume.
Potential reduce by 126.2 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 126.2 kB or 88% of the original size.
Potential reduce by 93.0 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. Imagine Brick images are well optimized though.
Potential reduce by 33.2 kB
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 6.3 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. Imaginebrick.com has all CSS files already compressed.
Number of requests can be reduced by 21 (34%)
62
41
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imagine Brick. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
imaginebrick.com
282 ms
joomla-fontawesome.min.css
24 ms
theme_animate.css
47 ms
template.min.css
76 ms
swiper.min.css
65 ms
joomla-alert.min.css
67 ms
jquery.min.js
88 ms
swiper.min.js
90 ms
menu-es5.min.js
119 ms
core.min.js
89 ms
template.min.js
89 ms
messages-es5.min.js
102 ms
user.js
123 ms
messages.min.js
111 ms
smartslider.min.css
112 ms
css
29 ms
n2.min.js
122 ms
smartslider-frontend.min.js
125 ms
ss-simple.min.js
133 ms
smartslider-backgroundanimation.min.js
242 ms
w-arrow-image.min.js
139 ms
joomla-alert.css
81 ms
analytics.js
19 ms
ib_logo5.jpg
52 ms
phone-60.png
51 ms
email-60.png
52 ms
06101707-specialty-after-7A.jpeg
54 ms
06040307-wall-after-1A.jpeg
110 ms
04070299-mailbox-after-1A.jpeg
60 ms
12092728-after-1.jpeg
109 ms
07082313-veneer-after-2E.jpeg
68 ms
10032312-repairs-after-1.jpeg
69 ms
06020103-outdoor_kitchen-after-1A.jpeg
109 ms
03030199-entrance-after-1A.jpeg
111 ms
06042101-porch-after-1A.jpeg
114 ms
03100703-natural_stone-after-1A.jpeg
111 ms
06040402-paver-after-1A.jpeg
134 ms
10111401-after-1.jpeg
133 ms
15011303-after-1.jpeg
135 ms
10_IMG_2488.jpeg
115 ms
18131050-after-1.jpeg
118 ms
18131001-after-1.jpeg
134 ms
06020103-outdoor_kitchen-after-1E.jpeg
139 ms
10092015-after-1.jpeg
139 ms
07090702-natural_stone-after-11E.jpeg
177 ms
09110213-after-1E.jpeg
169 ms
15011303-after-1.jpeg
169 ms
03010101-natural_stone-after-1E.jpeg
170 ms
icon-facebook-ipad.jpg
170 ms
IMG_0366.jpeg
171 ms
IMG_0575.jpeg
179 ms
cracks-2.jpeg
180 ms
cracks-3.jpeg
178 ms
cracks-1.jpeg
181 ms
icon-cracks.jpeg
182 ms
Repair-ABefore.jpeg
221 ms
Repair-AAfter.jpeg
219 ms
icon-engineered.jpeg
202 ms
collect
17 ms
Repair-CBefore.jpeg
182 ms
IMG_8009.jpeg
184 ms
Repair-CAfter.jpeg
184 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
16 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
34 ms
fa-solid-900.woff
225 ms
fa-regular-400.woff
195 ms
js
82 ms
imaginebrick.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
imaginebrick.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
Missing source maps for large first-party JavaScript
imaginebrick.com SEO score
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 Imaginebrick.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 Imaginebrick.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.
imaginebrick.com
Open Graph data is detected on the main page of Imagine Brick. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: