7.1 sec in total
111 ms
6.8 sec
181 ms
Click here to check amazing Stone Locator content for United States. Otherwise, check out these important facts you probably never knew about stonelocator.com
Visit stonelocator.comWe analyzed Stonelocator.com page load time and found that the first response time was 111 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
stonelocator.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.9 s
1/100
25%
Value5.8 s
50/100
10%
Value590 ms
50/100
30%
Value0.087
93/100
15%
Value10.2 s
25/100
10%
111 ms
54 ms
7 ms
7 ms
1100 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 51% of them (47 requests) were addressed to the original Stonelocator.com, 3% (3 requests) were made to Apexchat.net and 3% (3 requests) were made to Pixel.prfct.co. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Cnzz.mmstat.com.
Page size can be reduced by 514.7 kB (32%)
1.6 MB
1.1 MB
In fact, the total size of Stonelocator.com main page is 1.6 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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 79.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. This page needs HTML code to be minified as it can gain 11.8 kB, which is 13% 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 79.2 kB or 85% of the original size.
Potential reduce by 73.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. Stone Locator images are well optimized though.
Potential reduce by 269.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 269.0 kB or 69% of the original size.
Potential reduce by 93.1 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. Stonelocator.com needs all CSS files to be minified and compressed as it can save up to 93.1 kB or 86% of the original size.
Number of requests can be reduced by 72 (85%)
85
13
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stone Locator. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
stonelocator.com
111 ms
styles.css
54 ms
fonts.css
7 ms
style-blue.css
7 ms
z_stat.php
1100 ms
jquery.min.js
8 ms
jquery-1.6.min.js
420 ms
jquery-1.8.2.min.js
436 ms
flexslider.css
7 ms
jquery.flexslider.js
46 ms
modernizr.js
24 ms
jquery.easing.js
22 ms
jquery.mousewheel.js
12 ms
menu-mobile.css
115 ms
jquery.mmenu.css
151 ms
jquery.mmenu.js
228 ms
jquery.fancybox-1.3.4.js
271 ms
jquery.fancybox-1.3.4.css
216 ms
si.js
56 ms
swap.js
9 ms
invitation.ashx
296 ms
ico1.jpg
158 ms
divi.jpg
214 ms
ico2.jpg
243 ms
ico3.jpg
281 ms
ico5.png
341 ms
ico6.png
303 ms
ico4.jpg
367 ms
icon-houzz.jpg
319 ms
logo.jpg
361 ms
searchicon.png
388 ms
lc_bottom_visa.gif
390 ms
lc_bottom_mc.gif
407 ms
lc_bottom_discover.gif
413 ms
lc_bottom_amex.gif
415 ms
fnd.jpg
7 ms
bg_36.jpg
518 ms
bg_92.jpg
509 ms
bg_93.jpg
506 ms
bg_94.jpg
477 ms
cat1.jpg
93 ms
cat2.jpg
109 ms
cat3.jpg
286 ms
cat4.jpg
309 ms
cat7.jpg
409 ms
cat8.jpg
448 ms
divivert.jpg
437 ms
btn-submit.jpg
448 ms
apexchat.js
200 ms
stat.htm
161 ms
core.php
1324 ms
9.gif
1578 ms
gtm.js
133 ms
labelpict.png
30 ms
smarticon
100 ms
texgyreadventor-regular-webfont.woff
96 ms
5385e5bc30eacc45be0000e4.js
95 ms
invitation2.ashx
152 ms
fbevents.js
74 ms
5385e5bc30eacc45be0000e4.js
40 ms
gtm.js
76 ms
z_stat.php
563 ms
core.php
457 ms
si.js
76 ms
swap_session.js
213 ms
analytics.js
10 ms
141 ms
166 ms
collect
32 ms
tagjs
38 ms
collect
26 ms
collect
100 ms
77 ms
Pug
81 ms
adsct
117 ms
pixel
72 ms
cb
19 ms
tap.php
7 ms
pixel
16 ms
cb
3 ms
sd
23 ms
cb
3 ms
ncm
3 ms
9.gif
2892 ms
stat.htm
165 ms
app.gif
1229 ms
default_Tara_Formal.png
69 ms
transparent_blank.png
15 ms
stonelocator.com
87 ms
close_1.png
8 ms
chat.png
9 ms
app.gif
615 ms
404.php
87 ms
stonelocator.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
stonelocator.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
stonelocator.com SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stonelocator.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stonelocator.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.
stonelocator.com
Open Graph description is not detected on the main page of Stone Locator. 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: