Tools & Wizards About Us
epilogue.net screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

epilogue.net

Epilogue - Fantasy and Sci-fi at their best.

Page Load Speed

1 sec in total

First Response

93 ms

Resources Loaded

662 ms

Page Rendered

253 ms

epilogue.net screenshot

About Website

Visit epilogue.net now to see the best up-to-date Epilogue content for Russia and also check out these interesting facts you probably never knew about epilogue.net

Epilogue is a juried art gallery and artist community featuring only the best art. Our mission is to help Artists become more successful, assist Art Directors in finding new talent, and introduce Art ...

Visit epilogue.net

Key Findings

We analyzed Epilogue.net page load time and found that the first response time was 93 ms and then it took 915 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

epilogue.net performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

epilogue.net

93 ms

www.epilogue.net

91 ms

css_f4cdb2c12b178150a49799119f8b9029_0.css

17 ms

jquery.min.js

34 ms

js_35fe98714e5c202cde1fb9d9888a1caa_2.js

15 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 24% of them (12 requests) were addressed to the original Epilogue.net, 37% (18 requests) were made to Sbb.epilogue.net and 24% (12 requests) were made to Devi-delavie.epilogue.net. The less responsive or slowest element that took the longest time to load (266 ms) relates to the external source Sbb.epilogue.net.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Epilogue.net main page is 2.0 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. 50% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 55.4 kB

  • Original 68.5 kB
  • After minification 68.3 kB
  • After compression 13.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. 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 55.4 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 86.8 kB

  • Original 1.0 MB
  • After minification 924.9 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. Epilogue images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 309.5 kB

  • Original 471.1 kB
  • After minification 465.3 kB
  • After compression 161.6 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 309.5 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 344.5 kB

  • Original 420.2 kB
  • After minification 406.2 kB
  • After compression 75.7 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. Epilogue.net needs all CSS files to be minified and compressed as it can save up to 344.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (13%)

Requests Now

47

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

epilogue.net

epilogue.net

93 ms

www.epilogue.net

www.epilogue.net

91 ms

css_f4cdb2c12b178150a49799119f8b9029_0.css

css_f4cdb2c12b178150a49799119f8b9029_0.css

17 ms

jquery.min.js

jquery.min.js

34 ms

js_35fe98714e5c202cde1fb9d9888a1caa_2.js

js_35fe98714e5c202cde1fb9d9888a1caa_2.js

15 ms

js_2b6ed29d9088a260b4d5a474c1acca1d_0.js

js_2b6ed29d9088a260b4d5a474c1acca1d_0.js

13 ms

css_4a7abe221b80f649f341bd8d9da94d08_0.css

css_4a7abe221b80f649f341bd8d9da94d08_0.css

113 ms

gpt.js

gpt.js

103 ms

15528_1048050000.jpg

15528_1048050000.jpg

146 ms

9809_1120968000.jpg

9809_1120968000.jpg

138 ms

ga.js

ga.js

76 ms

29361_1074747600.jpg

29361_1074747600.jpg

98 ms

9546_1045371600.jpg

9546_1045371600.jpg

170 ms

16015_1161316800.jpg

16015_1161316800.jpg

115 ms

24938_1325566800.jpg

24938_1325566800.jpg

116 ms

10479_1055736000.jpg

10479_1055736000.jpg

117 ms

9962_993009600.jpg

9962_993009600.jpg

152 ms

27626_1204520400.jpg

27626_1204520400.jpg

165 ms

43238_1268712000.jpg

43238_1268712000.jpg

170 ms

47760_1376340639.jpg

47760_1376340639.jpg

170 ms

44356_1323752400.jpg

44356_1323752400.jpg

199 ms

19414_1035781200.jpg

19414_1035781200.jpg

214 ms

35466_1219204800.jpg

35466_1219204800.jpg

98 ms

9328_1028001600.jpg

9328_1028001600.jpg

116 ms

9324_1007269200.jpg

9324_1007269200.jpg

117 ms

20740_1057723200.jpg

20740_1057723200.jpg

143 ms

39152_1220760000.jpg

39152_1220760000.jpg

158 ms

23244_1083124800.jpg

23244_1083124800.jpg

165 ms

8822_1120708800.jpg

8822_1120708800.jpg

164 ms

16186_1066536000.jpg

16186_1066536000.jpg

192 ms

18806_1112245200.jpg

18806_1112245200.jpg

208 ms

11502_1000008000.jpg

11502_1000008000.jpg

208 ms

19792_1043125200.jpg

19792_1043125200.jpg

212 ms

30944_1083297600.jpg

30944_1083297600.jpg

219 ms

30192_1077858000.jpg

30192_1077858000.jpg

221 ms

44989_1343275200.jpg

44989_1343275200.jpg

246 ms

26975_1062993600.jpg

26975_1062993600.jpg

263 ms

39677_1287720000.jpg

39677_1287720000.jpg

264 ms

19741_1042174800.jpg

19741_1042174800.jpg

266 ms

bg_items.png

bg_items.png

25 ms

icons.png

icons.png

26 ms

logo.png

logo.png

25 ms

social_32x32.png

social_32x32.png

25 ms

loading.gif

loading.gif

26 ms

controls.png

controls.png

25 ms

pubads_impl_81.js

pubads_impl_81.js

21 ms

__utm.gif

__utm.gif

27 ms

container.html

container.html

10 ms

nr-852.min.js

nr-852.min.js

63 ms

Accessibility Review

epilogue.net accessibility score

100

Accessibility Issues

Best Practices

epilogue.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

epilogue.net SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epilogue.net 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 Epilogue.net 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

epilogue.net

Open Graph data is detected on the main page of Epilogue. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: