Tools & Wizards About Us
holycrossstore.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

holycrossstore.com

Page Load Speed

12.6 sec in total

First Response

942 ms

Resources Loaded

11.4 sec

Page Rendered

225 ms

holycrossstore.com screenshot

About Website

Visit holycrossstore.com now to see the best up-to-date Holycrossstore content and also check out these interesting facts you probably never knew about holycrossstore.com

Bless your house with one of our outstanding Holy Crucifix, blessed by the church the Holy Sepulchre.

Visit holycrossstore.com

Key Findings

We analyzed Holycrossstore.com page load time and found that the first response time was 942 ms and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

holycrossstore.com performance score

0

Network Requests Diagram

www.holycrossstore.com

942 ms

style.css

324 ms

styles.css

144 ms

style-wpec.css

261 ms

mobile-styles.css

199 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 59% of them (42 requests) were addressed to the original Holycrossstore.com, 25% (18 requests) were made to Livesupporti.com and 3% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (942 ms) belongs to the original domain Holycrossstore.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 574.9 kB (40%)

Content Size

1.4 MB

After Optimization

855.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Holycrossstore.com main page is 1.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. 55% of websites need less resources to load. Images take 656.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 36.6 kB

  • Original 46.7 kB
  • After minification 37.9 kB
  • After compression 10.1 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 8.7 kB, which is 19% 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 36.6 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 18.4 kB

  • Original 656.7 kB
  • After minification 638.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. Holycrossstore images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 343.2 kB

  • Original 514.8 kB
  • After minification 504.8 kB
  • After compression 171.5 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 343.2 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 176.7 kB

  • Original 212.1 kB
  • After minification 197.9 kB
  • After compression 35.4 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. Holycrossstore.com needs all CSS files to be minified and compressed as it can save up to 176.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (70%)

Requests Now

66

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Holycrossstore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.holycrossstore.com

www.holycrossstore.com

942 ms

style.css

style.css

324 ms

styles.css

styles.css

144 ms

style-wpec.css

style-wpec.css

261 ms

mobile-styles.css

mobile-styles.css

199 ms

custom_styles.css

custom_styles.css

134 ms

jquery.js

jquery.js

349 ms

jquery-migrate.min.js

jquery-migrate.min.js

275 ms

modernizr.min.js

modernizr.min.js

359 ms

respond.min.js

respond.min.js

275 ms

audio.min.js

audio.min.js

407 ms

style.css

style.css

393 ms

script.js

script.js

398 ms

jquery.form.min.js

jquery.form.min.js

334 ms

scripts.js

scripts.js

333 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

410 ms

jquery.touchSwipe.js

jquery.touchSwipe.js

523 ms

jquery.carouFredSel-packed.js

jquery.carouFredSel-packed.js

524 ms

jquery-ui.min.js

jquery-ui.min.js

51 ms

video.min.js

video.min.js

675 ms

jquery.isotope.min.js

jquery.isotope.min.js

562 ms

theme.min.js

theme.min.js

607 ms

wp-e-commerce.js

wp-e-commerce.js

657 ms

wp-embed.min.js

wp-embed.min.js

609 ms

conversion.js

conversion.js

29 ms

client.js

client.js

224 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

324 ms

site-bg.png

site-bg.png

345 ms

dc.js

dc.js

29 ms

backgrown19801.jpg

backgrown19801.jpg

596 ms

logo.png

logo.png

340 ms

timthumb.php

timthumb.php

583 ms

timthumb.php

timthumb.php

584 ms

timthumb.php

timthumb.php

595 ms

timthumb.php

timthumb.php

595 ms

all.js

all.js

269 ms

top-strip-bg.png

top-strip-bg.png

572 ms

top-nav-hover-bg.png

top-nav-hover-bg.png

576 ms

sprite.png

sprite.png

788 ms

header-cart-bg.png

header-cart-bg.png

587 ms

social-media-bg-repeat.png

social-media-bg-repeat.png

587 ms

nav-bg.png

nav-bg.png

786 ms

dashed-line.png

dashed-line.png

786 ms

testimonial-bg.png

testimonial-bg.png

786 ms

sansation_light-webfont.woff

sansation_light-webfont.woff

771 ms

sansation_regular-webfont.woff

sansation_regular-webfont.woff

772 ms

__utm.gif

__utm.gif

11 ms

276 ms

xd_arbiter.php

xd_arbiter.php

284 ms

xd_arbiter.php

xd_arbiter.php

528 ms

244 ms

parentChatGUI.css

parentChatGUI.css

18 ms

animate.min.css

animate.min.css

28 ms

jquery.ba-postmessage.min.js

jquery.ba-postmessage.min.js

24 ms

clientCrossdomainFunctions.js

clientCrossdomainFunctions.js

26 ms

clientGUI.htm

clientGUI.htm

208 ms

233 ms

message-cart-icon.png

message-cart-icon.png

282 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

31 ms

ClientGUI.js

ClientGUI.js

48 ms

ajaxfileupload.js

ajaxfileupload.js

29 ms

jquery.client.js

jquery.client.js

29 ms

ClientAjaxStub.htm

ClientAjaxStub.htm

80 ms

ClientResponseHandler.ashx

ClientResponseHandler.ashx

74 ms

classic-close-chat2-sprite.png

classic-close-chat2-sprite.png

14 ms

classic-popup-chat2-sprite.png

classic-popup-chat2-sprite.png

9 ms

agent-no-pic.png

agent-no-pic.png

14 ms

classic-send-file-visitor-sprite.png

classic-send-file-visitor-sprite.png

15 ms

emoticons-selector.png

emoticons-selector.png

22 ms

classic-visitor-cog-sprite.png

classic-visitor-cog-sprite.png

17 ms

43 ms

SEO Factors

holycrossstore.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Holycrossstore.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Holycrossstore.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.

Social Sharing Optimization

holycrossstore.com

Open Graph description is not detected on the main page of Holycrossstore. 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: