Tools & Wizards About Us
hickoryrecord.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 0

    Best Practices

  • 90

    SEO

    Google-friendlier than
    68% of websites

hickoryrecord.com

Hickory News | Hickory, North Carolina | Read Hickory, NC and North Carolina breaking news. Get latest news, events and information on North Carolina ...

Page Load Speed

3 sec in total

First Response

24 ms

Resources Loaded

2.3 sec

Page Rendered

637 ms

hickoryrecord.com screenshot

About Website

Visit hickoryrecord.com now to see the best up-to-date Hickory Record content for United States and also check out these interesting facts you probably never knew about hickoryrecord.com

Read Hickory, NC, North Carolina news from the Hickory Daily Record. Get headlines on local weather, entertainment, and events.

Visit hickoryrecord.com

Key Findings

We analyzed Hickoryrecord.com page load time and found that the first response time was 24 ms and then it took 2.9 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

hickoryrecord.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value5,850 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.878

3/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

hickoryrecord.com

24 ms

hickoryrecord.com

82 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

95 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

122 ms

lee.ds.css

90 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 22% of them (17 requests) were addressed to the original Hickoryrecord.com, 31% (24 requests) were made to Bloximages.newyork1.vip.townnews.com and 8% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 553.6 kB (48%)

Content Size

1.2 MB

After Optimization

605.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hickoryrecord.com main page is 1.2 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. 70% of websites need less resources to load. HTML takes 551.3 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 500.6 kB

  • Original 551.3 kB
  • After minification 455.0 kB
  • After compression 50.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 96.3 kB, which is 17% 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 500.6 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 16.0 kB
  • After minification 16.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. Hickory Record images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 37.3 kB

  • Original 512.3 kB
  • After minification 512.2 kB
  • After compression 475.0 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

-20%

Potential reduce by 15.7 kB

  • Original 79.4 kB
  • After minification 79.4 kB
  • After compression 63.6 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. Hickoryrecord.com needs all CSS files to be minified and compressed as it can save up to 15.7 kB or 20% of the original size.

Requests Breakdown

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

Requests Now

58

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hickory Record. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hickoryrecord.com

hickoryrecord.com

24 ms

hickoryrecord.com

hickoryrecord.com

82 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

95 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

122 ms

lee.ds.css

lee.ds.css

90 ms

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

114 ms

owl.carousel.d631cca58a0d014854c4a6c1815f1da3.css

owl.carousel.d631cca58a0d014854c4a6c1815f1da3.css

101 ms

osano.js

osano.js

119 ms

access.d7adebba498598b0ec2c.js

access.d7adebba498598b0ec2c.js

42 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

111 ms

user.js

user.js

74 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

142 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

149 ms

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

157 ms

application.3c64d611e594b45dd35b935162e79d85.js

application.3c64d611e594b45dd35b935162e79d85.js

157 ms

polyfill.min.js

polyfill.min.js

1076 ms

apstag.js

apstag.js

84 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

151 ms

hickoryrecord.com.v2.js

hickoryrecord.com.v2.js

148 ms

owl.carousel.50dc41fa734414148ce4b489fd904c5f.js

owl.carousel.50dc41fa734414148ce4b489fd904c5f.js

150 ms

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

156 ms

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

160 ms

firebase-app.js

firebase-app.js

94 ms

firebase-messaging.js

firebase-messaging.js

146 ms

messaging.js

messaging.js

80 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

153 ms

tracking.js

tracking.js

81 ms

prebid8.39.0.js

prebid8.39.0.js

158 ms

lee.common.js

lee.common.js

174 ms

fontawesome.568f3d1ab17b33ce05854081baadadac.js

fontawesome.568f3d1ab17b33ce05854081baadadac.js

181 ms

tracker.js

tracker.js

106 ms

op.js

op.js

85 ms

hickoryrecord.com.js

hickoryrecord.com.js

157 ms

dfp.lazy.ozone.js

dfp.lazy.ozone.js

159 ms

apstag.js

apstag.js

79 ms

gtm.js

gtm.js

76 ms

analytics.js

analytics.js

21 ms

gtm.js

gtm.js

26 ms

gtm.js

gtm.js

72 ms

publisher:getClientId

publisher:getClientId

83 ms

collect

collect

45 ms

collect

collect

148 ms

destination

destination

26 ms

d1f54158-a0b5-11ec-b63a-9760476d0bdc.png

d1f54158-a0b5-11ec-b63a-9760476d0bdc.png

95 ms

syd-logo.png

syd-logo.png

92 ms

%7B%7Bimage%7D%7D

%7B%7Bimage%7D%7D

90 ms

user_no_avatar.82c8fc38eb25dca10493a994ca1bfb90.png

user_no_avatar.82c8fc38eb25dca10493a994ca1bfb90.png

91 ms

logo-tagline.png

logo-tagline.png

93 ms

tracker.gif

tracker.gif

88 ms

gtm.js

gtm.js

102 ms

48 ms

analytics.min.js

analytics.min.js

71 ms

46 ms

94 ms

serif-ds.woff

serif-ds.woff

95 ms

88 ms

5b5dc540-ca6c-013a-51e3-0cc47a8ffaac

5b5dc540-ca6c-013a-51e3-0cc47a8ffaac

223 ms

settings

settings

16 ms

200 ms

js

js

91 ms

linkid.js

linkid.js

7 ms

60 ms

iframe

iframe

234 ms

179 ms

collect

collect

161 ms

collect

collect

160 ms

870.bundle.6e2976b75e60ab2b2bf8.js

870.bundle.6e2976b75e60ab2b2bf8.js

11 ms

tsub-middleware.bundle.77315eced46c5ae4c052.js

tsub-middleware.bundle.77315eced46c5ae4c052.js

11 ms

ml.gz.js

ml.gz.js

13 ms

13 ms

ga-audiences

ga-audiences

141 ms

i

i

22 ms

rubicon

rubicon

22 ms

pixel

pixel

36 ms

pixel

pixel

24 ms

google

google

3 ms

appnexus

appnexus

5 ms

Accessibility Review

hickoryrecord.com accessibility score

100

Accessibility Issues

SEO Factors

hickoryrecord.com SEO score

90

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

hickoryrecord.com

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