8.3 sec in total
1.9 sec
5.9 sec
540 ms
Click here to check amazing Hilltop Granite content. Otherwise, check out these important facts you probably never knew about hilltopgranite.com
Visit hilltopgranite.comWe analyzed Hilltopgranite.com page load time and found that the first response time was 1.9 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hilltopgranite.com performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value15.1 s
0/100
25%
Value19.0 s
0/100
10%
Value5,520 ms
0/100
30%
Value0.472
18/100
15%
Value21.7 s
1/100
10%
1883 ms
115 ms
252 ms
219 ms
362 ms
Our browser made a total of 195 requests to load all elements on the main page. We found that 70% of them (136 requests) were addressed to the original Hilltopgranite.com, 25% (48 requests) were made to Fonts.gstatic.com and 3% (5 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Hilltopgranite.com.
Page size can be reduced by 581.8 kB (15%)
3.9 MB
3.3 MB
In fact, the total size of Hilltopgranite.com main page is 3.9 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 148.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 148.2 kB or 87% of the original size.
Potential reduce by 101.5 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. Hilltop Granite images are well optimized though.
Potential reduce by 11.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. This website has mostly compressed JavaScripts.
Potential reduce by 321.0 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. Hilltopgranite.com needs all CSS files to be minified and compressed as it can save up to 321.0 kB or 58% of the original size.
Number of requests can be reduced by 80 (58%)
137
57
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hilltop Granite. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
hilltopgranite.com
1883 ms
wp-emoji-release.min.js
115 ms
style.min.css
252 ms
styles.css
219 ms
rs6.css
362 ms
header-footer-elementor.css
232 ms
elementor-icons.min.css
296 ms
animations.min.css
295 ms
frontend-legacy.min.css
288 ms
frontend.min.css
511 ms
post-1.css
320 ms
post-5950.css
423 ms
frontend.css
437 ms
post-6413.css
367 ms
post-6322.css
391 ms
style.css
440 ms
modules.min.css
908 ms
dripicons.css
463 ms
style.min.css
491 ms
fontawesome-all.min.css
547 ms
ionicons.min.css
533 ms
style.css
599 ms
style.css
561 ms
simple-line-icons.css
580 ms
mediaelementplayer-legacy.min.css
581 ms
wp-mediaelement.min.css
592 ms
style_dynamic.css
664 ms
modules-responsive.min.css
661 ms
style_dynamic_responsive.css
648 ms
css
76 ms
core-dashboard.min.css
669 ms
css
86 ms
fontawesome.min.css
731 ms
solid.min.css
727 ms
regular.min.css
728 ms
brands.min.css
729 ms
jquery.min.js
795 ms
jquery-migrate.min.js
798 ms
css
58 ms
font-awesome.css
764 ms
pe-icon-7-stroke.css
693 ms
rbtools.min.js
664 ms
rs6.min.js
787 ms
scripts.js
627 ms
core.min.js
593 ms
tabs.min.js
584 ms
mediaelement-and-player.min.js
719 ms
mediaelement-migrate.min.js
693 ms
wp-mediaelement.min.js
647 ms
jquery.appear.js
646 ms
modernizr.min.js
622 ms
hoverIntent.min.js
924 ms
jquery.plugin.js
902 ms
owl.carousel.min.js
904 ms
jquery.waypoints.min.js
884 ms
jquery.nicescroll.min.js
856 ms
fluidvids.min.js
803 ms
perfect-scrollbar.jquery.min.js
804 ms
ScrollToPlugin.min.js
790 ms
parallax.min.js
788 ms
jquery.waitforimages.js
770 ms
jquery.prettyPhoto.js
768 ms
jquery.easing.1.3.js
759 ms
isotope.pkgd.min.js
750 ms
packery-mode.pkgd.min.js
704 ms
swiper.min.js
690 ms
jquery.parallax-scroll.js
691 ms
modules.min.js
694 ms
wp-embed.min.js
627 ms
frontend.js
626 ms
webpack.runtime.min.js
626 ms
frontend-modules.min.js
621 ms
dialog.min.js
562 ms
waypoints.min.js
561 ms
share-link.min.js
561 ms
frontend.min.js
562 ms
preloaded-elements-handlers.min.js
491 ms
rsz_ht_logo_gold-1.png
332 ms
transparent.png
419 ms
coollogo_com-128201773.gif
420 ms
1-7.jpg
422 ms
3-7.jpg
440 ms
4-7.jpg
423 ms
2-7.jpg
424 ms
80.jpg
425 ms
3-1.jpg
1053 ms
4-1.jpg
121 ms
6-1.jpg
485 ms
5-1.jpg
732 ms
2-1.jpg
796 ms
1-1.jpg
794 ms
7-1.jpg
792 ms
1.jpg
795 ms
2.jpg
922 ms
White-Galaxy-Granite.jpg
1007 ms
5.jpg
920 ms
1-1.png
909 ms
2-1.png
907 ms
3-2.png
907 ms
4-2.png
999 ms
6-1.png
998 ms
5-2.png
996 ms
7-2.png
1001 ms
8-2.png
999 ms
Granite-VS-EQS-min-1024x724-1.jpeg
1000 ms
granit-color1.jpg
1058 ms
Loacation-Page-2.jpg
1057 ms
60.jpg
1054 ms
1-2.jpg
1054 ms
7.jpg
1053 ms
2-2.jpg
1055 ms
50.jpg
1073 ms
3-2.jpg
1074 ms
11.jpg
990 ms
4-2.jpg
1083 ms
12.jpg
1023 ms
90.jpg
1080 ms
10.png
1079 ms
9.png
1114 ms
1.png
1093 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
626 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
684 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
675 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
682 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
682 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
681 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
680 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
681 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
783 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
781 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jjPKsOdC6.ttf
783 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jvvKsOdC6.ttf
683 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8j4PKsOdC6.ttf
781 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jPvKsOdC6.ttf
783 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jvvOsOdC6.ttf
784 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jYPWsOdC6.ttf
786 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jWfWsOdC6.ttf
791 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jPvWsOdC6.ttf
784 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jF_WsOdC6.ttf
785 ms
Pe-icon-7-stroke.woff
1109 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
783 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
785 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
786 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
788 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
786 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
785 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
787 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
789 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
790 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
790 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
790 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
790 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
790 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
791 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
792 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf
791 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf
793 ms
fontawesome-webfont.woff
1230 ms
fa-solid-900.woff
724 ms
1f4cd.svg
342 ms
fa-solid-900.woff
590 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf
176 ms
fa-regular-400.woff
494 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
125 ms
fa-regular-400.woff
538 ms
eicons.woff
566 ms
fa-brands-400.woff
565 ms
fa-brands-400.woff
598 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf
121 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf
121 ms
4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlbgv5qvmSA.ttf
121 ms
4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlbSv5qvmSA.ttf
122 ms
4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlY-uJqvmSA.ttf
122 ms
4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlYHuJqvmSA.ttf
120 ms
iframe_api
139 ms
4UacrEBBsBhlBjvfkQjt71kZfyBzPgNG9hU49aqm.ttf
123 ms
4UacrEBBsBhlBjvfkQjt71kZfyBzPgNGxBU49aqm.ttf
107 ms
4UacrEBBsBhlBjvfkQjt71kZfyBzPgNGKBI49aqm.ttf
106 ms
4UacrEBBsBhlBjvfkQjt71kZfyBzPgNGERI49aqm.ttf
107 ms
8.png
714 ms
7.png
711 ms
5.png
711 ms
4.png
701 ms
6.png
622 ms
3e.png
620 ms
2.png
621 ms
rsz_ht_logo_gold_round-1.png
620 ms
HT-Round-Footer-1.png
618 ms
simple_button_pattern.png
616 ms
www-widgetapi.js
9 ms
ko-wGRIsWWQ
112 ms
www-player.css
100 ms
www-embed-player.js
116 ms
base.js
136 ms
fetch-polyfill.js
99 ms
hilltopgranite.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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hilltopgranite.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
Detected JavaScript libraries
Page has valid source maps
hilltopgranite.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
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 Hilltopgranite.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 Hilltopgranite.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.
hilltopgranite.com
Open Graph description is not detected on the main page of Hilltop Granite. 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: