4.2 sec in total
853 ms
2.7 sec
609 ms
Visit cathedral.shop now to see the best up-to-date CATHEDRAL content and also check out these interesting facts you probably never knew about cathedral.shop
Visit cathedral.shopWe analyzed Cathedral.shop page load time and found that the first response time was 853 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cathedral.shop performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value12.0 s
0/100
25%
Value8.6 s
17/100
10%
Value400 ms
67/100
30%
Value0.041
99/100
15%
Value11.4 s
19/100
10%
853 ms
177 ms
359 ms
537 ms
684 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 43% of them (20 requests) were addressed to the original Cathedral.shop, 26% (12 requests) were made to Makeshop-multi-images.akamaized.net and 9% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (962 ms) belongs to the original domain Cathedral.shop.
Page size can be reduced by 120.9 kB (6%)
1.9 MB
1.8 MB
In fact, the total size of Cathedral.shop main page is 1.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. 75% 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 36.6 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 14.7 kB, which is 32% 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 80% of the original size.
Potential reduce by 83.2 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. CATHEDRAL images are well optimized though.
Potential reduce by 247 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.
Potential reduce by 793 B
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. Cathedral.shop needs all CSS files to be minified and compressed as it can save up to 793 B or 28% of the original size.
Number of requests can be reduced by 20 (45%)
44
24
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CATHEDRAL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
cathedral.shop
853 ms
remodal.css
177 ms
remodal-default-theme.css
359 ms
jquery.bxslider.min.css
537 ms
system-4-1-2-980d04db36c1f1d505aaa4e6e3bb15e4.css
684 ms
js
67 ms
icon
35 ms
user-4-1-2-e1ff870487b72e0e93fb716895b8cff8.css
728 ms
jquery.min.js
27 ms
user-4-1-2-62c3aa3bba7399b95fb14fa147d00c59.js
729 ms
jquery.min.js
729 ms
remodal.min.js
678 ms
jquery.bxslider.min.js
738 ms
system-4-1-2-7a6adff2dfd5abfb0b6c038a022ec2f2.js
962 ms
analytics.js
71 ms
slide1.png
590 ms
000000002348_VKzL5GS.jpg
278 ms
000000002347_Yfqofax.jpg
283 ms
000000002346_WgkrMRg.jpg
300 ms
000000002345_tzdWlTh.jpg
347 ms
000000002344_dzHzLYi.jpg
352 ms
000000002343_59nLmuO.jpg
345 ms
000000002342_1aW56js.jpg
343 ms
000000002341_WzFPyub.jpg
343 ms
000000002340_8nJ2aRS.jpg
344 ms
000000002338_FTlXy38.jpg
350 ms
000000002337_RH5TlmC.jpg
353 ms
000000002336_5p5gUTG.jpg
440 ms
icon-instagram.svg
279 ms
icon-facebook.svg
280 ms
js
155 ms
css
70 ms
notosansjapanese.css
80 ms
cart
363 ms
collect
173 ms
collect
244 ms
collect
190 ms
flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf
239 ms
js
73 ms
bx_loader.gif
186 ms
controls.png
183 ms
system-4-1-6-980d04db36c1f1d505aaa4e6e3bb15e4.css
187 ms
user-4-1-6-f0366b8a78faf6ce50b7a7914cf84c7b.css
209 ms
user-4-1-6-9a84e1f03253480a9ca4eedf1e4271d8.js
206 ms
system-4-1-6-7a6adff2dfd5abfb0b6c038a022ec2f2.js
205 ms
collect
54 ms
cathedral.shop accessibility score
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
<object> elements do not have alternate text
cathedral.shop 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
cathedral.shop SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cathedral.shop can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Cathedral.shop 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.
cathedral.shop
Open Graph description is not detected on the main page of CATHEDRAL. 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: