Tools & Wizards About Us
journal.epic.my screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

journal.epic.my

Epic Journal - Stories for communities - Epic Journal

Page Load Speed

2.7 sec in total

First Response

42 ms

Resources Loaded

2.5 sec

Page Rendered

100 ms

journal.epic.my screenshot

About Website

Visit journal.epic.my now to see the best up-to-date Journal Epic content for Malaysia and also check out these interesting facts you probably never knew about journal.epic.my

Journalling stories of people overcoming social challenges and sharing knowledge for a cooperative society. These are stories for communities.

Visit journal.epic.my

Key Findings

We analyzed Journal.epic.my page load time and found that the first response time was 42 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

journal.epic.my performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

journal.epic.my

42 ms

journal.epic.my

345 ms

gtm.js

113 ms

style.min.css

324 ms

view.css

277 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 55% of them (35 requests) were addressed to the original Journal.epic.my, 31% (20 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Journal.epic.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.6 kB (24%)

Content Size

233.5 kB

After Optimization

176.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Journal.epic.my main page is 233.5 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. 60% of websites need less resources to load. CSS take 149.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 46.4 kB

  • Original 58.7 kB
  • After minification 57.1 kB
  • After compression 12.3 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 46.4 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 19.4 kB
  • After minification 19.4 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. Journal Epic images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 44 B

  • Original 5.5 kB
  • After minification 5.5 kB
  • After compression 5.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 10.1 kB

  • Original 149.9 kB
  • After minification 147.9 kB
  • After compression 139.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. Journal.epic.my has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (85%)

Requests Now

41

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

journal.epic.my

journal.epic.my

42 ms

journal.epic.my

journal.epic.my

345 ms

gtm.js

gtm.js

113 ms

style.min.css

style.min.css

324 ms

view.css

view.css

277 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

280 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

284 ms

styles.css

styles.css

763 ms

js_composer.min.css

js_composer.min.css

294 ms

css

css

46 ms

bootstrap.css

bootstrap.css

562 ms

icons.css

icons.css

552 ms

plugins.css

plugins.css

547 ms

theme-23fa328649.css

theme-23fa328649.css

574 ms

style.css

style.css

559 ms

jetpack.css

jetpack.css

829 ms

jquery.min.js

jquery.min.js

820 ms

jquery-migrate.min.js

jquery-migrate.min.js

1351 ms

css

css

62 ms

email-decode.min.js

email-decode.min.js

565 ms

prettyPhoto.min.css

prettyPhoto.min.css

813 ms

owl.min.css

owl.min.css

857 ms

animate.min.css

animate.min.css

1015 ms

w.js

w.js

39 ms

tracks-callables.js

tracks-callables.js

1583 ms

image-cdn.js

image-cdn.js

1093 ms

index.js

index.js

1092 ms

index.js

index.js

1584 ms

plugins.js

plugins.js

1268 ms

scripts.js

scripts.js

1842 ms

js_composer_front.min.js

js_composer_front.min.js

1346 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

2008 ms

owl.carousel.min.js

owl.carousel.min.js

1617 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

1624 ms

underscore.min.js

underscore.min.js

1854 ms

waypoints.min.js

waypoints.min.js

1855 ms

vc_grid.min.js

vc_grid.min.js

1882 ms

Logo-small.png

Logo-small.png

769 ms

EPIC-Logo-RGB-01.png

EPIC-Logo-RGB-01.png

567 ms

EPIC-Logo-02-2.png

EPIC-Logo-02-2.png

388 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

62 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

72 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

114 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

124 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

124 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

128 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

129 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

127 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

127 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

150 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

149 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

149 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

149 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

151 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

151 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

150 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

151 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

152 ms

socicon.ttf

socicon.ttf

731 ms

sdk.js

sdk.js

54 ms

g.gif

g.gif

29 ms

sdk.js

sdk.js

15 ms

Accessibility Review

journal.epic.my accessibility score

91

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

journal.epic.my best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

journal.epic.my SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Journal.epic.my 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 Journal.epic.my 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

journal.epic.my

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