2.8 sec in total
391 ms
2.1 sec
286 ms
Click here to check amazing Epica content for United States. Otherwise, check out these important facts you probably never knew about epica.com
Discover premium handcrafted journals at Epica. Elevate your writing experience with our exquisite collection designed to inspire creativity and organization.
Visit epica.comWe analyzed Epica.com page load time and found that the first response time was 391 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
epica.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value7.9 s
3/100
25%
Value3.7 s
85/100
10%
Value2,570 ms
4/100
30%
Value0.002
100/100
15%
Value13.8 s
10/100
10%
391 ms
107 ms
89 ms
154 ms
189 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Epica.com, 47% (36 requests) were made to Cdn.shopify.com and 8% (6 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (590 ms) relates to the external source Cdn.shopify.com.
Page size can be reduced by 680.4 kB (70%)
967.9 kB
287.5 kB
In fact, the total size of Epica.com main page is 967.9 kB. 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. CSS take 551.1 kB which makes up the majority of the site volume.
Potential reduce by 58.7 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.2 kB, which is 11% 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 58.7 kB or 76% of the original size.
Potential reduce by 134.4 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 134.4 kB or 40% of the original size.
Potential reduce by 487.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. Epica.com needs all CSS files to be minified and compressed as it can save up to 487.3 kB or 88% of the original size.
Number of requests can be reduced by 55 (86%)
64
9
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epica. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
epica.com
391 ms
epica.com
107 ms
js
89 ms
classic-10_7.css
154 ms
theme.scss
189 ms
vendor.js
201 ms
theme.js
213 ms
bootstrap.min.css
212 ms
jquery.fancybox.css
200 ms
custom-style.css
204 ms
font-awesome.scss
303 ms
bootstrap4-addon.scss
276 ms
load_feature-24ff1222c9aa13bb217653c0d3ea28c40a796a280e6da29ad421eec2a6075c86.js
232 ms
storefront-21b5dddfc8b64c1ad68cee3ba7448d1ffa15c24e969ebc1fbccf1a3784b659ad.js
232 ms
features-87e8399988880142f2c62771b9d8f2ff6c290b3ff745dd426eb0dfe0db9d1dae.js
254 ms
bold-upsell.css
267 ms
bold-upsell-custom.css
317 ms
bold-options.css
268 ms
options.js
255 ms
bold-helper-functions.js
298 ms
bold.css
416 ms
jquery.min.js
183 ms
js.cookie.js
430 ms
1029.js
231 ms
ls.unveilhooks.js
468 ms
lazysizes.min.js
565 ms
responsivevoice.js
572 ms
jquery.fancybox.js
570 ms
custom.js
570 ms
bootstrap.min.js
562 ms
form.js
562 ms
jquery.pjax.js
590 ms
conversion.js
221 ms
conversion_async.js
127 ms
322 ms
trekkie.storefront.min.js
267 ms
shop_events_listener-d81deda6557a113fbcc6a993184828adcef6f241e4ca52b6a21169cb03169317.js
266 ms
epica-logo.png
308 ms
Fira-Sans-regular.woff
212 ms
Fira-Sans-500.woff
211 ms
Fira-Sans-300.woff
214 ms
Fira-Sans-700.woff
211 ms
fontawesome-webfont.woff
212 ms
glyphicons-halflings-regular.woff
579 ms
253 ms
227 ms
analytics.js
228 ms
consent-tracking-api-legacy.js
89 ms
session
225 ms
klaviyo.js
304 ms
fbevents.js
78 ms
analytics.js
145 ms
core.js
213 ms
73 ms
vck.js
278 ms
shopify-boomerang-1.0.0.min.js
20 ms
session
458 ms
287475391657136
82 ms
js
134 ms
main.2424edb5.js
256 ms
248 ms
account_version_check.html
240 ms
klaviyo_analytics.js
232 ms
modules
225 ms
collect
41 ms
collect
125 ms
105 ms
112 ms
mwgt_4.1.js
66 ms
ga-audiences
43 ms
onsite
15 ms
0.7cfa86ad6aae84df1f18.css
16 ms
styles.1757ddef7c8731c410e2.js
43 ms
sentry.5ae9269795f89fbb9935.js
86 ms
vendors~signupForms.d73b1e68bbd199f3ffc8.js
85 ms
signupForms.0381c4cc194cf6a244b2.js
84 ms
epica.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.
epica.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
Page has valid source maps
epica.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epica.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 Epica.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.
epica.com
Open Graph data is detected on the main page of Epica. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: