Tools & Wizards About Us
epi365.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

epi365.com

South Carolina News & Charleston SC News | Post and Courier | Charleston, SC. Local News, Sports and Weather

Page Load Speed

4.8 sec in total

First Response

46 ms

Resources Loaded

3.8 sec

Page Rendered

1 sec

epi365.com screenshot

About Website

Click here to check amazing Epi 365 content. Otherwise, check out these important facts you probably never knew about epi365.com

South Carolina news reported from Charleston, Columbia, Greenville, Spartanburg, Myrtle Beach, Hilton Head and North Augusta. Read stories on crime, politics, food and business.

Visit epi365.com

Key Findings

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

Performance Metrics

epi365.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value57.7 s

0/100

10%

TBT (Total Blocking Time)

Value7,970 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.158

73/100

15%

TTI (Time to Interactive)

Value34.0 s

0/100

10%

Network Requests Diagram

epi365.com

46 ms

www.postandcourier.com

22 ms

www.postandcourier.com

99 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

116 ms

layout.b46cef82bac6c2a77ca1f12b4c79fc8a.css

134 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Epi365.com, 20% (17 requests) were made to Bloximages.newyork1.vip.townnews.com and 11% (9 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Sdk.mrf.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 935.2 kB (51%)

Content Size

1.8 MB

After Optimization

897.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Epi365.com main page is 1.8 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. 80% 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. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 461.7 kB

  • Original 526.0 kB
  • After minification 456.1 kB
  • After compression 64.4 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 70.0 kB, which is 13% 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 461.7 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 20.0 kB
  • After minification 20.0 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. Epi 365 images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 460.9 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 760.8 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 460.9 kB or 38% of the original size.

CSS Optimization

-19%

Potential reduce by 12.6 kB

  • Original 65.1 kB
  • After minification 65.1 kB
  • After compression 52.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. Epi365.com needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (74%)

Requests Now

73

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

epi365.com

epi365.com

46 ms

www.postandcourier.com

www.postandcourier.com

22 ms

www.postandcourier.com

www.postandcourier.com

99 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

116 ms

layout.b46cef82bac6c2a77ca1f12b4c79fc8a.css

layout.b46cef82bac6c2a77ca1f12b4c79fc8a.css

134 ms

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

145 ms

ipw6blv.css

ipw6blv.css

147 ms

access.d7adebba498598b0ec2c.js

access.d7adebba498598b0ec2c.js

90 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

124 ms

user.js

user.js

124 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

124 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

132 ms

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

138 ms

application.3c64d611e594b45dd35b935162e79d85.js

application.3c64d611e594b45dd35b935162e79d85.js

131 ms

polyfill.min.js

polyfill.min.js

640 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

145 ms

gpt.js

gpt.js

207 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

142 ms

tracking.js

tracking.js

121 ms

fontawesome.568f3d1ab17b33ce05854081baadadac.js

fontawesome.568f3d1ab17b33ce05854081baadadac.js

144 ms

script.js

script.js

140 ms

script.js

script.js

140 ms

postandcourier.js

postandcourier.js

140 ms

load.js

load.js

210 ms

adsbygoogle.js

adsbygoogle.js

220 ms

4286221.js

4286221.js

141 ms

js

js

197 ms

tracker.js

tracker.js

138 ms

copypastesubscribeformlogic.js

copypastesubscribeformlogic.js

134 ms

tnt.ads.core.06f66657baee8dcc28d4650bb59ec82f.js

tnt.ads.core.06f66657baee8dcc28d4650bb59ec82f.js

141 ms

smartquotes.js

smartquotes.js

132 ms

p.css

p.css

52 ms

gtm.js

gtm.js

92 ms

gtm.js

gtm.js

120 ms

analytics.js

analytics.js

40 ms

gtm.js

gtm.js

61 ms

gtm.js

gtm.js

93 ms

js

js

109 ms

publisher:getClientId

publisher:getClientId

135 ms

collect

collect

17 ms

collect

collect

85 ms

231

231

513 ms

gtm.js

gtm.js

240 ms

advertising.js

advertising.js

642 ms

js

js

236 ms

fbevents.js

fbevents.js

318 ms

marfeel-sdk.es5.js

marfeel-sdk.es5.js

1591 ms

ce8b064e-d79f-11ec-92e8-075c1166f897.png

ce8b064e-d79f-11ec-92e8-075c1166f897.png

216 ms

3e9a35da-37da-11ea-8b94-f7f8d91c3495.png

3e9a35da-37da-11ea-8b94-f7f8d91c3495.png

217 ms

65e75d99399ab.preview.jpg

65e75d99399ab.preview.jpg

215 ms

65e23fdc6454a.image.jpg

65e23fdc6454a.image.jpg

215 ms

pubads_impl.js

pubads_impl.js

597 ms

show_ads_impl.js

show_ads_impl.js

525 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

518 ms

leadflows.js

leadflows.js

1218 ms

4286221.js

4286221.js

573 ms

banner.js

banner.js

579 ms

tracker.gif

tracker.gif

139 ms

492 ms

d

d

271 ms

d

d

401 ms

search.png

search.png

280 ms

js

js

266 ms

uwt.js

uwt.js

1206 ms

id59w4jdho

id59w4jdho

1134 ms

741dd5e9be713798244f799d0d621eee

741dd5e9be713798244f799d0d621eee

139 ms

collect

collect

140 ms

d

d

143 ms

d

d

143 ms

d

d

783 ms

d

d

877 ms

d

d

877 ms

collect

collect

892 ms

c31cbc9d415b722b823de363b31195d7

c31cbc9d415b722b823de363b31195d7

256 ms

LB-Zone-1

LB-Zone-1

326 ms

424 ms

142953540

142953540

503 ms

clarity.js

clarity.js

81 ms

ga-audiences

ga-audiences

222 ms

adsct

adsct

214 ms

adsct

adsct

212 ms

AGSKWxX5Eh8P9N4k0_CLlBgkv-yuDWwAEpiw0XbndLy_466f_-bK45Riq73oy8BWqNVFIJvDDL8d_AhymxTtC4aYtid8q1XliTMnGe1BcSOqDWJhyrGnQHtGNq2qsX6VPlgnO60fCLG0

AGSKWxX5Eh8P9N4k0_CLlBgkv-yuDWwAEpiw0XbndLy_466f_-bK45Riq73oy8BWqNVFIJvDDL8d_AhymxTtC4aYtid8q1XliTMnGe1BcSOqDWJhyrGnQHtGNq2qsX6VPlgnO60fCLG0

65 ms

AGSKWxVTTXBDpkKToWEX5inzbFurXcQkj_jbBqX5C0ioRJKAlntNiLumkQkusjFgycy1SGWDv_JOYZ8sidg8oP9_WvTWMQGhS0g1ldFDIBGi-ykZaoAVYoS5xTUjDVH0kqIWE98lkTSp

AGSKWxVTTXBDpkKToWEX5inzbFurXcQkj_jbBqX5C0ioRJKAlntNiLumkQkusjFgycy1SGWDv_JOYZ8sidg8oP9_WvTWMQGhS0g1ldFDIBGi-ykZaoAVYoS5xTUjDVH0kqIWE98lkTSp

98 ms

load

load

158 ms

231

231

268 ms

Accessibility Review

epi365.com accessibility score

90

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

epi365.com best practices score

83

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

epi365.com SEO score

93

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

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 Epi365.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 Epi365.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

epi365.com

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