thetennesseegazette.com

thetennesseegazette.com is SSL secured

Free website and domain report on thetennesseegazette.com

Last Updated: 25th July, 2023 Update Now
Overview

Snoop Summary for thetennesseegazette.com

This is a free and comprehensive report about thetennesseegazette.com. The domain thetennesseegazette.com is currently hosted on a server located in United States with the IP address 23.253.216.18, where USD is the local currency and the local language is English. Our records indicate that thetennesseegazette.com is privately registered by Domains By Proxy, LLC. If thetennesseegazette.com was to be sold it would possibly be worth $154 USD (based on the daily revenue potential of the website over a 24 month period). Thetennesseegazette.com receives an estimated 69 unique visitors every day - a small amount of traffic. This report was last updated 25th July, 2023.

About thetennesseegazette.com

Site Preview: thetennesseegazette.com thetennesseegazette.com
Title:
Description:
Keywords and Tags:
Related Terms:
Fav Icon:
Age: Over 3 years old
Domain Created: 22nd July, 2021
Domain Updated: 23rd July, 2022
Domain Expires: 22nd July, 2023
Review

Snoop Score

1/5

Valuation

$154 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 8,763,573
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 3
Moz Page Authority: 4

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 69
Monthly Visitors: 2,100
Yearly Visitors: 25,185
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $6 USD
Yearly Revenue: $72 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: thetennesseegazette.com 23
Domain Name: thetennesseegazette 19
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 68
Performance 69
Accessibility 73
Best Practices 92
SEO 82
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
69

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for thetennesseegazette.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 2.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 30 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://thetennesseegazette.com/
http/1.1
0
113.14200004563
278
0
301
text/html
https://www.thetennesseegazette.com/
http/1.1
113.4290000191
322.05700001214
2022
4144
200
text/html
Document
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700&display=swap
h2
330.35000006203
348.63200003747
1510
8601
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
h2
330.53300005849
348.03200000897
1421
4396
200
text/css
Stylesheet
https://www.thetennesseegazette.com/config.js
http/1.1
330.72700002231
575.33000002149
2209
1909
200
text/javascript
Script
https://www.thetennesseegazette.com/_nuxt/de63ad4.js
http/1.1
331.65900001768
445.85200003348
1452
2348
200
application/javascript
Script
https://www.thetennesseegazette.com/_nuxt/94129ef.js
http/1.1
331.99500001501
597.78200008441
239116
834450
200
application/javascript
Script
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
http/1.1
332.18100003432
610.80600006972
89841
970207
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
h2
579.84800008126
605.33600009512
52116
139004
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
h2
640.97599999513
666.93500010297
73701
205207
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
645.35300002899
650.56199999526
20631
50205
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
862.53400007263
867.34800005797
11956
11028
200
font/woff2
Font
https://js.stripe.com/v3
h2
881.95100007579
904.34600005392
77699
326494
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=2092336200&t=pageview&_s=1&dl=https%3A%2F%2Fwww.thetennesseegazette.com%2F&ul=en-us&de=UTF-8&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAEABAAAAAC~&jid=1740076893&gjid=588819056&cid=1843679761.1658336830&tid=UA-241914-10&_gid=889885476.1658336830&_r=1&gtm=2wg7i0KGCXW2X&cd1=thetennesseegazette.com&cd2=1&z=1985558634
h2
918.10100001749
923.42900007498
625
1
200
text/plain
XHR
https://www.google-analytics.com/g/collect?v=2&tid=G-5VG3FMDW9W&gtm=2oe7i0&_p=2092336200&_z=ccd.v9B&cid=1843679761.1658336830&ul=en-us&sr=800x600&_s=1&sid=1658336829&sct=1&seg=0&dl=https%3A%2F%2Fwww.thetennesseegazette.com%2F&dt=&en=page_view&_fv=1&_ss=1
970.86300002411
975.9100000374
0
0
-1
Ping
https://www.thetennesseegazette.com/v1/token/thetennesseegazette/new
http/1.1
1029.205000028
1162.8260000143
570
77
200
application/json
XHR
https://js.stripe.com/v3/m-outer-b264dce0f6b368bd152098cad6b3c755.html
h2
1037.0630000252
1054.1420000372
1620
240
200
text/html
Document
https://js.stripe.com/v3/fingerprinted/js/m-outer-1f270b8fd2c2e3cf8410a1ea3ccb1934.js
h2
1065.5350000598
1083.1650000764
1350
1535
200
text/javascript
Script
https://m.stripe.network/inner.html
h2
1089.0709999949
1105.5770000676
1573
930
200
text/html
Document
https://m.stripe.network/out-4.5.42.js
h2
1118.5410000617
1146.4550000383
14905
88253
200
text/javascript
Script
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/4206774-tennessee-gazette-logo-1090525x188601.svg
http/1.1
1335.2960000047
2001.1750000995
8562
29005
200
image/svg+xml
Image
https://www.thetennesseegazette.com/firebase-link-qr.svg
http/1.1
1335.6510000303
1541.0760000814
1173
2534
200
image/svg+xml
Image
https://www.awltovhc.com/image-100448887-14462353-1614360201000
http/1.1
1344.3510000361
1425.6090000272
503
0
302
text/html
https://www.thetennesseegazette.com/v1/press-releases/thetennesseegazette?offset=0
http/1.1
1346.2220000802
2229.7820000676
3692
17513
200
application/json
XHR
https://www.thetennesseegazette.com/v1/articles/thetennesseegazette?limit=20&offset=0
http/1.1
1347.233000095
2101.0050000623
6351
17325
200
application/json
XHR
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1356.5660000313
1360.7860000338
11968
11040
200
font/woff2
Font
https://www.yceml.net/0401/14462353-1645768812806
http/1.1
1425.9000000311
2183.793000062
68335
68145
200
image/jpeg
Image
https://m.stripe.com/6
h2
2064.8340000771
2403.5810000496
661
156
200
application/json
XHR
https://www.thetennesseegazette.com/news.png
http/1.1
2121.2610000512
2291.3780000526
2646
2390
200
image/png
Image
https://www.lduhtrp.net/image-100448887-10789422-1614116850000
http/1.1
2139.737999998
2600.1850001048
491
0
302
text/html
data
2139.688000083
2140.0020000292
0
42
200
image/gif
Image
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8648425-582142111-635662059982009683-JW-Flash-050215-Sports-B-100x57.jpeg
http/1.1
2152.6650000596
2369.4170000963
2513
2115
200
image/jpeg
Image
https://www.awltovhc.com/image-100448887-10386906-1623696292000
http/1.1
2280.9540000744
2714.4200000912
506
0
302
text/html
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8642212-582103110-60461331-0-image-a-12_1658263263993-100x60.jpeg
http/1.1
2338.5650001001
2614.5440000109
2957
2559
200
image/jpeg
Image
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8628151-582011297-c56a80ec-1620-485f-ac89-f42787c9f691-070622_ct_hot_dogs_12-100x56.jpeg
http/1.1
2340.1900000172
2590.7570000272
2973
2575
200
image/jpeg
Image
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8613712-581913668-1658172651_081816b00-russell-3_gs_t1070_h3e59e184c2b4c5b4b7b789f0cec677bbf2b2960f-100x82.jpeg
http/1.1
2346.6900000349
2654.0150000947
2662
2264
200
image/jpeg
Image
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8637159-kutless-twenty-900x900.jpeg
http/1.1
2351.5340000158
3231.1860000482
184932
184531
200
image/jpeg
Image
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8631907-pam-with-sign-900x1120.png
http/1.1
2351.6330000712
2665.4090000084
1908557
1908156
200
image/png
Image
https://www.yceml.net/0558/10789422-1645818987506
http/1.1
2600.640000077
2761.6790001048
24396
24206
200
image/gif
Image
https://www.yceml.net/0474/10386906-1645818782519
http/1.1
2714.7340000374
2807.106000022
13805
13615
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
366.967
11.93
618.839
5.749
624.603
6.633
658.885
8.515
667.983
20.699
689.62
16.859
707.98
214.701
935.186
24.33
961.96
52.142
1017.318
11.634
1030.054
39.956
1098.452
6.998
1149.46
7.246
1192.716
109.451
1303.33
12.882
1316.364
11.723
1330.381
58.806
1389.322
21.706
2081.07
24.189
2142.462
40.828
2183.362
8.702
2273.631
48.884
2322.674
14.266
2819.381
5.273
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Thetennesseegazette.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Thetennesseegazette.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Thetennesseegazette.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Thetennesseegazette.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images — Potential savings of 46 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.yceml.net/0401/14462353-1645768812806
68145
47123
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 210 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.thetennesseegazette.com/
209.623
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Thetennesseegazette.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://thetennesseegazette.com/
190
https://www.thetennesseegazette.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Thetennesseegazette.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 14 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.thetennesseegazette.com/_nuxt/94129ef.js
14570
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
141
https://js.stripe.com/v3
40
https://m.stripe.network/out-4.5.42.js
31
Avoids an excessive DOM size — 496 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
496
Maximum DOM Depth
18
Maximum Child Elements
22
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Thetennesseegazette.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.thetennesseegazette.com/
215.114
8.83
1.508
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
209.298
182.665
13.225
https://www.thetennesseegazette.com/_nuxt/94129ef.js
202.768
152.706
11.572
https://m.stripe.network/inner.html
125.988
119.696
1.06
Unattributable
67.686
2.653
0.145
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
67.003
62.63
3.181
Minimizes main-thread work — 1.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
638.128
Other
136.517
Style & Layout
94.843
Rendering
90.447
Script Parsing & Compilation
42.208
Parse HTML & CSS
12.208
Garbage Collection
11.667
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 39 requests • 2,776 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
39
2842278
Image
12
2223511
Script
10
573020
Font
2
23924
Other
10
13677
Document
3
5215
Stylesheet
2
2931
Media
0
0
Third-party
28
2492928
Minimize third-party usage — Third-party code blocked the main thread for 40 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
97808
43.797
2113156
0
125817
0
26855
0
21256
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.12021276595745
0.085481481481481
0.01604097714736
0.01604097714736
0.00062940898345154
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 4 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://m.stripe.network/out-4.5.42.js
2239
109
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
1352
107
https://www.thetennesseegazette.com/_nuxt/94129ef.js
2052
59
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
1143
52
Avoid non-composited animations — 7 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
 
 
 
 
 
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of thetennesseegazette.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 2.2 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.239
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources — Potential savings of 230 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Thetennesseegazette.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700&display=swap
1510
230
https://www.thetennesseegazette.com/config.js
2209
70
Reduce unused JavaScript — Potential savings of 250 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.thetennesseegazette.com/_nuxt/94129ef.js
239116
150466
https://js.stripe.com/v3
77699
56147
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
73701
28483
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
52116
20673
Avoid enormous network payloads — Total size was 2,776 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8631907-pam-with-sign-900x1120.png
1908557
https://www.thetennesseegazette.com/_nuxt/94129ef.js
239116
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8637159-kutless-twenty-900x900.jpeg
184932
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
89841
https://js.stripe.com/v3
77699
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
73701
https://www.yceml.net/0401/14462353-1645768812806
68335
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
52116
https://www.yceml.net/0558/10789422-1645818987506
24396
https://www.google-analytics.com/analytics.js
20631

Metrics

First Contentful Paint — 1.6 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 2.5 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 1.7 s
The time taken for the primary content of the page to be rendered.

Other

Properly size images — Potential savings of 1,787 KiB
Images can slow down the page's load time. Thetennesseegazette.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8631907-pam-with-sign-900x1120.png
1908156
1673453
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8637159-kutless-twenty-900x900.jpeg
184531
156285
Serve images in next-gen formats — Potential savings of 1,806 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8631907-pam-with-sign-900x1120.png
1908156
1741005.7
https://www.yceml.net/0401/14462353-1645768812806
68145
58488.7
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8637159-kutless-twenty-900x900.jpeg
184531
49954.25
Preload Largest Contentful Paint image — Potential savings of 830 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8637159-kutless-twenty-900x900.jpeg
830
Serve static assets with an efficient cache policy — 19 resources found
Thetennesseegazette.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.thetennesseegazette.com/_nuxt/94129ef.js
0
239116
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
0
89841
https://www.thetennesseegazette.com/news.png
0
2646
https://www.thetennesseegazette.com/_nuxt/de63ad4.js
0
1452
https://js.stripe.com/v3
60000
77699
https://js.stripe.com/v3/fingerprinted/js/m-outer-1f270b8fd2c2e3cf8410a1ea3ccb1934.js
60000
1350
https://m.stripe.network/out-4.5.42.js
300000
14905
https://www.thetennesseegazette.com/firebase-link-qr.svg
1800000
1173
https://www.google-analytics.com/analytics.js
7200000
20631
https://www.yceml.net/0401/14462353-1645768812806
110533000
68335
https://www.yceml.net/0474/10386906-1645818782519
155231000
13805
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8648425-582142111-635662059982009683-JW-Flash-050215-Sports-B-100x57.jpeg
250277000
2513
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8628151-582011297-c56a80ec-1620-485f-ac89-f42787c9f691-070622_ct_hot_dogs_12-100x56.jpeg
259155000
2973
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8642212-582103110-60461331-0-image-a-12_1658263263993-100x60.jpeg
259165000
2957
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8613712-581913668-1658172651_081816b00-russell-3_gs_t1070_h3e59e184c2b4c5b4b7b789f0cec677bbf2b2960f-100x82.jpeg
259200000
2662
https://www.yceml.net/0558/10789422-1645818987506
432779000
24396
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8631907-pam-with-sign-900x1120.png
1143902000
1908557
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/8637159-kutless-twenty-900x900.jpeg
1182926000
184932
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/4206774-tennessee-gazette-logo-1090525x188601.svg
1200792000
8562
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/4206774-tennessee-gazette-logo-1090525x188601.svg
https://www.thetennesseegazette.com/firebase-link-qr.svg
https://www.thetennesseegazette.com/firebase-link-qr.svg
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of thetennesseegazette.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Thetennesseegazette.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that thetennesseegazette.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Vue
Nuxt.js
core-js
core-js-global@3.18.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://thetennesseegazette.com/
Allowed

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.thetennesseegazette.com/_nuxt/94129ef.js
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for thetennesseegazette.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of thetennesseegazette.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of thetennesseegazette.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of thetennesseegazette.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 64
Performance 33
Accessibility 81
Best Practices 92
SEO 85
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
33

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for thetennesseegazette.com. This includes details about optimizing page load times which can result in a better user experience.

Other

Properly size images
Images can slow down the page's load time. Thetennesseegazette.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Thetennesseegazette.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Thetennesseegazette.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Thetennesseegazette.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Thetennesseegazette.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images — Potential savings of 8 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.yceml.net/0824/15038264-1631123322581
39770
7857
Serve images in next-gen formats — Potential savings of 23 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.yceml.net/0824/15038264-1631123322581
39770
23482.15
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 180 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.thetennesseegazette.com/
183.337
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Thetennesseegazette.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://thetennesseegazette.com/
630
https://www.thetennesseegazette.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Thetennesseegazette.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 14 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.thetennesseegazette.com/_nuxt/94129ef.js
14570
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
141
https://js.stripe.com/v3
40
https://m.stripe.network/out-4.5.42.js
35
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 759 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.thetennesseegazette.com/_nuxt/94129ef.js
239116
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
89841
https://www.yceml.net/0859/12218203-1641421283719
83373
https://js.stripe.com/v3
77693
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
73684
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
52114
https://www.yceml.net/0824/15038264-1631123322581
39960
https://www.google-analytics.com/analytics.js
20631
https://m.stripe.network/out-4.5.42.js
16695
https://www.yceml.net/0131/11478147-1645817055531
15702
Avoids an excessive DOM size — 496 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
496
Maximum DOM Depth
18
Maximum Child Elements
22
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Thetennesseegazette.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 35 requests • 759 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
35
777338
Script
10
574778
Image
8
156886
Font
2
23924
Other
10
13702
Document
3
5071
Stylesheet
2
2977
Media
0
0
Third-party
24
427978
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.25947916666667
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 9 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
5730
280
https://m.stripe.network/out-4.5.42.js
8770
270
https://www.thetennesseegazette.com/_nuxt/94129ef.js
8009
173
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
4702
120
https://js.stripe.com/v3
7690
103
https://www.thetennesseegazette.com/_nuxt/94129ef.js
8362
103
https://m.stripe.network/out-4.5.42.js
9040
101
https://www.thetennesseegazette.com/_nuxt/94129ef.js
8692
72
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
3300
52
Avoid non-composited animations — 7 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
 
 
 
 
 
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of thetennesseegazette.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://thetennesseegazette.com/
http/1.1
0
88.897999958135
293
0
301
text/html
https://www.thetennesseegazette.com/
http/1.1
89.129999978468
271.46999997785
2022
4144
200
text/html
Document
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700&display=swap
h2
278.3000000054
296.11200001091
1510
8601
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
h2
278.43599999323
292.40799997933
1467
5292
200
text/css
Stylesheet
https://www.thetennesseegazette.com/config.js
http/1.1
278.63700001035
503.41199996183
2203
1903
200
text/javascript
Script
https://www.thetennesseegazette.com/_nuxt/de63ad4.js
http/1.1
278.85100001004
421.01699998602
1452
2348
200
application/javascript
Script
https://www.thetennesseegazette.com/_nuxt/94129ef.js
http/1.1
279.01599998586
559.06599998707
239116
834450
200
application/javascript
Script
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
http/1.1
279.19500001008
479.54599995865
89841
970207
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
h2
505.82099996973
534.09599995939
52114
139004
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
h2
557.15199996484
621.91599997459
73684
205207
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
560.2319999598
571.83799997438
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1401068734&t=pageview&_s=1&dl=https%3A%2F%2Fwww.thetennesseegazette.com%2F&ul=en-us&de=UTF-8&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAEABAAAAAC~&jid=1936173345&gjid=1228747987&cid=840275172.1658336848&tid=UA-241914-10&_gid=1054675750.1658336848&_r=1&gtm=2wg7i0KGCXW2X&cd1=thetennesseegazette.com&cd2=1&z=1263798762
h2
587.34099997673
597.86499995971
625
1
200
text/plain
XHR
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
720.38499999326
733.18699997617
11956
11028
200
font/woff2
Font
https://js.stripe.com/v3
h2
735.86899996735
754.86899999669
77693
326494
200
text/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-5VG3FMDW9W&gtm=2oe7i0&_p=1401068734&_z=ccd.v9B&cid=840275172.1658336848&ul=en-us&sr=360x640&_s=1&sid=1658336848&sct=1&seg=0&dl=https%3A%2F%2Fwww.thetennesseegazette.com%2F&dt=&en=page_view&_fv=1&_ss=1
779.98799999477
782.46499999659
0
0
-1
Ping
https://www.thetennesseegazette.com/v1/token/thetennesseegazette/new
http/1.1
818.32099996973
932.60900001042
571
77
200
application/json
XHR
https://js.stripe.com/v3/m-outer-b264dce0f6b368bd152098cad6b3c755.html
h2
826.48399996106
838.81899999687
1482
240
200
text/html
Document
https://js.stripe.com/v3/fingerprinted/js/m-outer-1f270b8fd2c2e3cf8410a1ea3ccb1934.js
h2
848.30599999987
861.21599999024
1349
1535
200
text/javascript
Script
https://m.stripe.network/inner.html
h2
865.11899996549
889.31499997852
1567
930
200
text/html
Document
https://m.stripe.network/out-4.5.42.js
h2
896.70499996282
923.11400000472
16695
88253
200
text/javascript
Script
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/4206774-tennessee-gazette-logo-1090525x188601.svg
http/1.1
1041.4109999547
1085.7609999948
8562
29005
200
image/svg+xml
Image
https://www.thetennesseegazette.com/firebase-link-qr.svg
http/1.1
1041.6090000072
1182.1239999845
1173
2534
200
image/svg+xml
Image
https://www.ftjcfx.com/image-100448887-12218203-1500390265000
http/1.1
1047.3609999754
1149.6509999852
503
0
302
text/html
https://www.thetennesseegazette.com/v1/press-releases/thetennesseegazette?offset=0
http/1.1
1048.6519999686
1206.7849999876
3692
17513
200
application/json
XHR
https://www.thetennesseegazette.com/v1/articles/thetennesseegazette?limit=20&offset=0
http/1.1
1049.2879999802
1203.0759999761
6351
17325
200
application/json
XHR
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1055.22499996
1065.9030000097
11968
11040
200
font/woff2
Font
https://www.yceml.net/0859/12218203-1641421283719
http/1.1
1150.0510000042
1192.0129999635
83373
83183
200
image/gif
Image
https://www.thetennesseegazette.com/news.png
http/1.1
1219.1159999929
1317.498999997
2646
2390
200
image/png
Image
https://www.tqlkg.com/image-100448887-15038264-1631123322000
http/1.1
1238.1659999955
1339.2959999619
503
0
302
text/html
data
1237.8000000026
1238.0269999849
0
42
200
image/gif
Image
https://www.ftjcfx.com/image-100448887-11478147-1623683972000
http/1.1
1265.3549999814
1366.34399998
503
0
302
text/html
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8648425-582142111-635662059982009683-JW-Flash-050215-Sports-B-100x57.jpeg
http/1.1
1276.9829999888
1320.859999978
2513
2115
200
image/jpeg
Image
https://www.yceml.net/0824/15038264-1631123322581
http/1.1
1339.5729999756
1361.4059999818
39960
39770
200
image/jpeg
Image
https://www.yceml.net/0131/11478147-1645817055531
http/1.1
1366.5310000069
1388.7919999543
15702
15512
200
image/gif
Image
https://m.stripe.com/6
h2
1437.2659999644
1527.6869999943
661
156
200
application/json
XHR
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8642212-582103110-60461331-0-image-a-12_1658263263993-100x60.jpeg
http/1.1
1438.1439999561
1479.8249999876
2957
2559
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
295.403
7.26
563.819
5.784
570.363
13.054
597.354
11.989
609.578
7.699
617.669
139.895
772.571
29.925
813.825
25.639
840.189
5.893
863.362
5.465
949.795
67.5
1017.672
9.028
1028.423
43.345
1071.846
11.257
1083.125
8.136
1224.806
36.227
1261.11
25.793
1286.916
10.319
1432.476
25.357
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Total Blocking Time — 480 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Reduce JavaScript execution time — 1.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
544.876
475.912
16.664
https://www.thetennesseegazette.com/_nuxt/94129ef.js
527.796
393.36
16.272
https://m.stripe.network/inner.html
346.084
329.284
2.456
https://www.thetennesseegazette.com/
307.392
17.752
4.024
Unattributable
175.944
12.088
1.156
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
146.952
137.196
6.732
https://js.stripe.com/v3
125.776
113.988
7
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
90
81.256
4.164
https://m.stripe.network/out-4.5.42.js
54.564
41.856
2.804
https://www.google-analytics.com/analytics.js
52.16
46.476
1.464
Minimize main-thread work — 2.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1663.52
Other
302.912
Style & Layout
226.404
Rendering
93.412
Script Parsing & Compilation
66.904
Garbage Collection
32.352
Parse HTML & CSS
31.064

Metrics

First Contentful Paint — 6.2 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 8.8 s
The time taken for the page to become fully interactive.
Speed Index — 6.2 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 8.3 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.259
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 280 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 6.6 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 930 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Thetennesseegazette.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700&display=swap
1510
780
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
1467
150
https://www.thetennesseegazette.com/config.js
2203
180
Reduce unused JavaScript — Potential savings of 250 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.thetennesseegazette.com/_nuxt/94129ef.js
239116
150466
https://js.stripe.com/v3
77693
56142
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
73684
28477
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
52114
20672
Serve static assets with an efficient cache policy — 15 resources found
Thetennesseegazette.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.thetennesseegazette.com/_nuxt/94129ef.js
0
239116
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
0
89841
https://www.thetennesseegazette.com/news.png
0
2646
https://www.thetennesseegazette.com/_nuxt/de63ad4.js
0
1452
https://js.stripe.com/v3
60000
77693
https://js.stripe.com/v3/fingerprinted/js/m-outer-1f270b8fd2c2e3cf8410a1ea3ccb1934.js
60000
1349
https://m.stripe.network/out-4.5.42.js
300000
16695
https://www.thetennesseegazette.com/firebase-link-qr.svg
1800000
1173
https://www.google-analytics.com/analytics.js
7200000
20631
https://www.yceml.net/0824/15038264-1631123322581
158418000
39960
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8648425-582142111-635662059982009683-JW-Flash-050215-Sports-B-100x57.jpeg
250308000
2513
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/8642212-582103110-60461331-0-image-a-12_1658263263993-100x60.jpeg
259172000
2957
https://www.yceml.net/0131/11478147-1645817055531
323313000
15702
https://www.yceml.net/0859/12218203-1641421283719
582938000
83373
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/4206774-tennessee-gazette-logo-1090525x188601.svg
1130901000
8562
Reduce the impact of third-party code — Third-party code blocked the main thread for 290 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
99447
227.872
125798
61.124
26901
0
21256
0
14032
0
1006
0
503
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/4206774-tennessee-gazette-logo-1090525x188601.svg
First Contentful Paint (3G) — 12460 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
81

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of thetennesseegazette.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Thetennesseegazette.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that thetennesseegazette.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Vue
Nuxt.js
core-js
core-js-global@3.18.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://thetennesseegazette.com/
Allowed

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.thetennesseegazette.com/_nuxt/94129ef.js
https://www.thetennesseegazette.com/_nuxt/3eb3ba1.js
85

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for thetennesseegazette.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of thetennesseegazette.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
30

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of thetennesseegazette.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of thetennesseegazette.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 23.253.216.18
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Rackspace Hosting
Registration

Domain Registrant

Private Registration: Yes
Name: Registration Private
Organization: Domains By Proxy, LLC
Country: US
City: Tempe
State: Arizona
Post Code: 85281
Email:
Phone: +1.4806242599
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.13.154.6
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.alabamanewsdispatch.com
Issued By: R3
Valid From: 26th January, 2023
Valid To: 26th April, 2023
Subject: CN = www.alabamanewsdispatch.com
Hash: a0c0a0a6
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03BC6292C63AD847DBE91C41AAFE805A2848
Serial Number (Hex): 03BC6292C63AD847DBE91C41AAFE805A2848
Valid From: 26th January, 2024
Valid To: 26th April, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Jan 26 05:19:22.911 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:65:CB:1F:26:BB:3B:24:1E:77:45:99:04:
BF:54:EF:E1:13:3C:CB:CA:6F:F4:0C:1E:54:B2:9D:71:
C2:5A:B2:2F:02:21:00:D3:85:AB:05:03:3C:25:1A:EA:
07:A2:04:C1:8E:8C:FF:0C:2E:87:3E:33:F5:52:76:55:
5F:DF:BF:A5:57:D6:48
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Jan 26 05:19:22.938 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:BF:01:A6:8C:BF:A0:FB:0F:17:D9:10:
B9:AB:5C:D5:BB:CC:24:4C:2F:16:BC:A0:96:5D:55:88:
8D:43:BB:F2:B1:02:21:00:BB:C4:CD:59:37:C9:85:00:
AD:B6:79:08:5F:B0:F1:3F:21:40:3D:C9:3A:CB:68:D7:
24:4F:06:35:94:13:89:EA
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.alaskapoliticaljournal.com
DNS:www.americansamoabusinessreport.com
DNS:www.arizonabusinesswatch.com
DNS:www.arkansashealthcarereport.com
DNS:www.baystateculturedaily.com
DNS:www.baystatetimes.com
DNS:www.coloradotourismtimes.com
DNS:www.connecticutartsreview.com
DNS:www.connecticuthealthdigest.com
DNS:www.culturallifekentucky.com
DNS:www.culturebeatsouthdakota.com
DNS:www.culturedigestmissouri.com
DNS:www.culturezonepuertorico.com
DNS:www.detroitnewsdigest.com
DNS:www.econewssouthcarolina.com
DNS:www.ecotimesvirginislands.com
DNS:www.entertainmentguidemissouri.com
DNS:www.entertainmentpresswashington.com
DNS:www.entertainmenttimesvirginia.com
DNS:www.environmenttodaynewhampshire.com
DNS:www.environmenttodayoklahoma.com
DNS:www.georgiabusinesstribune.com
DNS:www.guamenvironmentdaily.com
DNS:www.hawkeyepoliticstoday.com
DNS:www.healthylivingarizona.com
DNS:www.illinoislifestylenews.com
DNS:www.illinoistechjournal.com
DNS:www.indianabusinessreporter.com
DNS:www.industrydigestdc.com
DNS:www.industryinsidernebraska.com
DNS:www.industrytimeskansas.com
DNS:www.industrytodaywestvirginia.com
DNS:www.iowaculturebeat.com
DNS:www.iowaentertainmentweekly.com
DNS:www.iowahealthcarereporter.com
DNS:www.lifestylereviewnewmexico.com
DNS:www.louisianaadventurer.com
DNS:www.louisianahealthdaily.com
DNS:www.louisianatechreview.com
DNS:www.marylandenvironmenttoday.com
DNS:www.minnesotaenvironmentaltimes.com
DNS:www.minnesotaindustrynews.com
DNS:www.mississippidispatch.com
DNS:www.nationalcapitaldaily.com
DNS:www.nebraskabusinesspress.com
DNS:www.newhampshireartsentertainment.com
DNS:www.newhampshiretravelwire.com
DNS:www.newjerseybusinessjournal.com
DNS:www.newmexicohealthreporter.com
DNS:www.newyorktraveldaily.com
DNS:www.northcarolinaecowire.com
DNS:www.northdakotalifestyleweekly.com
DNS:www.northdakotatechnologyreview.com
DNS:www.northstarstatenews.com
DNS:www.oklahomaculturedaily.com
DNS:www.oklahomaindustrytimes.com
DNS:www.olddominiondispatch.com
DNS:www.politicalreporterguam.com
DNS:www.potomachealthnews.com
DNS:www.puertoricopoliticalbrief.com
DNS:www.rhodeislandbusinessdaily.com
DNS:www.rhodeislanddailypress.com
DNS:www.rhodeislandtechnologyweekly.com
DNS:www.rockymountainbusinessbrief.com
DNS:www.scitechworlddelaware.com
DNS:www.southcarolinalifestylereview.com
DNS:www.southcarolinascitechwire.com
DNS:www.southdakotaenvironmentalist.com
DNS:www.southdakotamorningstar.com
DNS:www.sunflowerstatenewswire.com
DNS:www.technologyjournalohio.com
DNS:www.techtodaywestvirginia.com
DNS:www.tennesseebusinessgazette.com
DNS:www.tennesseedailyjournal.com
DNS:www.tennesseejournaloftechnology.com
DNS:www.texanculturetoday.com
DNS:www.texasindustryjournal.com
DNS:www.theconcordtimes.com
DNS:www.thehartfordpost.com
DNS:www.thekansasexaminer.com
DNS:www.thekentuckytourist.com
DNS:www.themainereporter.com
DNS:www.themissouritravelguide.com
DNS:www.thenewjerseypost.com
DNS:www.theohiotravelguide.com
DNS:www.theolympiaobserver.com
DNS:www.thepennsylvaniapost.com
DNS:www.thetennesseegazette.com
DNS:www.thewyomingsun.com
DNS:www.topekagazette.com
DNS:www.utahenvironmentalpress.com
DNS:www.vermontentertainmentweek.com
DNS:www.vermontnewsjournal.com
DNS:www.virginislandsdigitalpress.com
DNS:www.virginislandsgazette.com
DNS:www.wellnesswirekansas.com
DNS:www.westvirginiapoliticsjournal.com
DNS:www.wventertainmentzone.com
DNS:www.wyominghealthcareweekly.com
DNS:www.alabamanewsdispatch.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
thetennesseegazette.com. 23.253.216.18 IN 10800

NS Records

Host Nameserver Class TTL
thetennesseegazette.com. ns3.newsmatics.com. IN 10800
thetennesseegazette.com. ns.newsmatics.com. IN 10800
thetennesseegazette.com. ns5.newsmatics.com. IN 10800

MX Records

Priority Host Server Class TTL
10 thetennesseegazette.com. mail1.cloud.ipdgroup.com. IN 10800
10 thetennesseegazette.com. mail6.cloud.ipdgroup.com. IN 10800
10 thetennesseegazette.com. mail2.cloud.ipdgroup.com. IN 10800

SOA Records

Domain Name Primary NS Responsible Email TTL
thetennesseegazette.com. ns.newsmatics.com. hostmaster.ein.cz. 10800

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 2nd March, 2023
Content-Type: text/html
Content-Length: 5020
Last-Modified: 2nd March, 2023
Connection: keep-alive
Keep-Alive: timeout=10
Vary: Accept-Encoding
ETag: "64005f97-139c"
Accept-Ranges: bytes

Whois Lookup

Created: 22nd July, 2021
Changed: 23rd July, 2022
Expires: 22nd July, 2023
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns.newsmatics.com
ns3.newsmatics.com
ns5.newsmatics.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
2155 E Warner Rd
Owner Post Code: 85284
Owner City: Tempe
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=thetennesseegazette.com
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
2155 E Warner Rd
Admin Post Code: 85284
Admin City: Tempe
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=thetennesseegazette.com
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
2155 E Warner Rd
Tech Post Code: 85284
Tech City: Tempe
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=thetennesseegazette.com
Full Whois: Domain Name: thetennesseegazette.com
Registry Domain ID: 2628624569_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2022-07-23T13:53:23Z
Creation Date: 2021-07-22T17:48:48Z
Registrar Registration Expiration Date: 2023-07-22T17:48:48Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 2155 E Warner Rd
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85284
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=thetennesseegazette.com
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 2155 E Warner Rd
Admin City: Tempe
Admin State/Province: Arizona
Admin Postal Code: 85284
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=thetennesseegazette.com
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 2155 E Warner Rd
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85284
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=thetennesseegazette.com
Name Server: NS.NEWSMATICS.COM
Name Server: NS3.NEWSMATICS.COM
Name Server: NS5.NEWSMATICS.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-03-02T16:35:04Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
ns.newsmatics.com 173.203.107.116
ns3.newsmatics.com 104.130.207.141
ns5.newsmatics.com 23.253.164.79
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5
0/5