4.3 sec in total
78 ms
3.7 sec
477 ms
Welcome to free-times.com homepage info - get ready to check Free Times best content for United States right away, or after learning these important things about free-times.com
Stay up to date on food, arts and events from The Free Times, covering the arts in Columbia and Richland County.
Visit free-times.comWe analyzed Free-times.com page load time and found that the first response time was 78 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
free-times.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value12.4 s
0/100
25%
Value16.2 s
0/100
10%
Value7,320 ms
0/100
30%
Value0
100/100
15%
Value39.8 s
0/100
10%
78 ms
81 ms
100 ms
98 ms
121 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Free-times.com, 11% (16 requests) were made to Bloximages.newyork1.vip.townnews.com and 8% (12 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Sdk.mrf.io.
Page size can be reduced by 849.8 kB (40%)
2.1 MB
1.3 MB
In fact, the total size of Free-times.com main page is 2.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 314.3 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 40.9 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 314.3 kB or 87% of the original size.
Potential reduce by 30.9 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Free Times needs image optimization as it can save up to 30.9 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 490.0 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 490.0 kB or 32% of the original size.
Potential reduce by 14.6 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Free-times.com needs all CSS files to be minified and compressed as it can save up to 14.6 kB or 20% of the original size.
Number of requests can be reduced by 88 (79%)
111
23
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Free Times. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 77 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
78 ms
bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css
81 ms
layout.5bce7eb56c23d79d6ab89ab093c281ea.css
100 ms
theme-basic.a7351649a9c39f0af7c6d288a87ef140.css
98 ms
ipw6blv.css
121 ms
css
90 ms
access.d7adebba498598b0ec2c.js
39 ms
jquery.min.d6d18fcf88750a16d256e72626e676a6.js
104 ms
user.js
79 ms
bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js
100 ms
common.08a61544f369cc43bf02e71b2d10d49f.js
101 ms
tnt.ee95c0b6f1daceb31bf5ef84353968c6.js
109 ms
application.3c64d611e594b45dd35b935162e79d85.js
113 ms
polyfill.min.js
442 ms
tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js
120 ms
gpt.js
178 ms
tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js
116 ms
tracking.js
100 ms
fontawesome.568f3d1ab17b33ce05854081baadadac.js
118 ms
script.js
106 ms
script.js
104 ms
postandcourier.js
104 ms
load.js
168 ms
adsbygoogle.js
173 ms
4286221.js
118 ms
js
111 ms
js
161 ms
tracker.js
105 ms
widget.min.js
435 ms
copypastesubscribeformlogic.js
111 ms
signup-form-widget.min.js
151 ms
tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js
107 ms
smartquotes.js
116 ms
tnt.regions.b44801b45845a81b995eeaad12f4f276.js
122 ms
p.css
37 ms
gtm.js
43 ms
gtm.js
67 ms
analytics.js
49 ms
gtm.js
44 ms
gtm.js
77 ms
js
72 ms
publisher:getClientId
471 ms
cs
1381 ms
gtm.js
421 ms
advertising.js
1375 ms
destination
374 ms
js
371 ms
fbevents.js
1154 ms
js
986 ms
marfeel-sdk.es5.js
1965 ms
d815f6ea-d4ac-11e9-9bd0-27c1fe1ff441.png
351 ms
7cdcdcfc-7520-11ea-93ca-538791ccb2e1.png
351 ms
pubads_impl.js
1110 ms
show_ads_impl.js
892 ms
banner.js
1221 ms
web-interactives-embed.js
890 ms
leadflows.js
1224 ms
4286221.js
886 ms
tracker.gif
188 ms
1134 ms
collect
440 ms
collect
725 ms
analytics.min.js
1057 ms
d
476 ms
d
989 ms
d
988 ms
search.png
643 ms
S6uyw4BMUTPHjx4wWA.woff
1291 ms
S6u9w4BMUTPHh7USSwiPHw.woff
1353 ms
S6u9w4BMUTPHh6UVSwiPHw.woff
1383 ms
d
661 ms
d
1161 ms
js
633 ms
uwt.js
1268 ms
id59w4jdho
1309 ms
collect
553 ms
8362.jsx
1231 ms
load
1200 ms
underscore-min.js
1005 ms
zrt_lookup.html
580 ms
collect
688 ms
434
593 ms
649 ms
142953540
264 ms
settings
63 ms
ga-audiences
144 ms
adsct
524 ms
adsct
521 ms
WidgetTemplate.min.css
91 ms
angular.min.js
328 ms
widgetcombined2.min.js
117 ms
clarity.js
115 ms
066e31344ece44c686ce73bbdbd926f8
80 ms
api.js
56 ms
870.bundle.6e2976b75e60ab2b2bf8.js
31 ms
tsub-middleware.bundle.77315eced46c5ae4c052.js
43 ms
p-uq0GLFySb_d1T.gif
428 ms
2e70184bb08afee7e14fa7af3090d71d
37 ms
LB-Zone-3
227 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
111 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
201 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
363 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
366 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
366 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
365 ms
icomoon.woff
11 ms
recaptcha__en.js
473 ms
m
759 ms
AGSKWxXIR_-WQtrjfRtZeqxuV9X_pSPhqmjGrDIURC_swGh8Hdw4FAwV5dhjjDI3YIMmZQe_-A3SQcmr7EmRPw1oVVWuTWa353EzZHeHaWEZlh8v1zDER8ypCUDel5PFqyNi2wRuWwS6
302 ms
uid2SecureSignal.js
370 ms
esp.js
455 ms
esp.js
370 ms
publishertag.ids.js
316 ms
connectId-gpt.js
370 ms
encrypted-tag-g.js
689 ms
sync.min.js
367 ms
pubcid.min.js
290 ms
434
351 ms
cs
172 ms
ajax-loader.gif
149 ms
aoKLuczkoke7prvhRXt7lQ.medium.png
120 ms
ada0ddcb-8462-4790-9b32-d4fcce29c5d4.medium.png
198 ms
GckoHaQ140y4vuanWh4SsA.medium.png
229 ms
PLLNHKjUr0SLnzzHCBqEbA.medium.png
204 ms
F7Q6OV9Q00-kOpTC2DR31w.medium.png
275 ms
YVC5rRW_HUe22rwYImA2Mg.medium.jpg
202 ms
HJiKuKWRj0u_b6ANzNjekA.medium.png
228 ms
6Dff6y-z_0mkcMgo51CjYg.medium.jpg
201 ms
iHBaCM0fokmpXCW3-xAMBQ.medium.jpg
203 ms
H4y56KsCT0OnmB9OhQyp_Q.medium.png
228 ms
j_pKDAwQA0m3NjJS2BF8Qw.medium.png
230 ms
ZeORdqPAsUGh5I98pzNZeg.medium.jpg
230 ms
4hbW5_NfWU6PJuscrGLxgQ.medium.jpg
250 ms
7KL9WptugEG0p5c6ePaikw.medium.png
273 ms
s-5hbn2kn0epH5pNCiDEqQ.medium.png
273 ms
ZzLeBfuXwke4jZshvvECww.medium.png
276 ms
ov3kIkOJg0WwBCJ1pqP3Fw.medium.png
277 ms
vA9aJa9tc06xm0xeZ9EsSg.medium.jpg
274 ms
XFJa8GyvCkyKbyIFeurc0Q.medium.jpg
275 ms
zgjK0Gck6ESDmdqICkwaiw.medium.png
276 ms
63f0202a-dd16-42d1-a045-60d094c8bf80.medium.png
279 ms
AGSKWxX1LOu3uSGfIYHtB2twADUNhu3261AC623h8INJRz-W728W7rmPRJCi66lMRJrlrU4DIuwDqeCT5mBZrO5jfHXVXbJN9iLyABjUgkKFBSPyXJTbm3xoMzAbUuoV3o5aVEcIq-r_
153 ms
map
135 ms
signup-form-widget.css
47 ms
13d0c5e270fb0d8b7b256e5b93ff1375.json
148 ms
sodar
72 ms
sodar2.js
42 ms
c.gif
24 ms
free-times.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
free-times.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
free-times.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Free-times.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Free-times.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
free-times.com
Open Graph data is detected on the main page of Free Times. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: