Tools & Wizards About Us
todayville.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

todayville.com

Red Deer News & Red Deer Events - Todayville.com

Page Load Speed

4.8 sec in total

First Response

176 ms

Resources Loaded

1.6 sec

Page Rendered

3 sec

todayville.com screenshot

About Website

Welcome to todayville.com homepage info - get ready to check Todayville best content for Canada right away, or after learning these important things about todayville.com

Red Deer News. Building community. Local stories, events and in-depth analysis on business, sports, arts and lifestyle. Click to contribute your story

Visit todayville.com

Key Findings

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

Performance Metrics

todayville.com performance score

0

Network Requests Diagram

todayville.com

176 ms

www.todayville.com

287 ms

style.min.css

328 ms

vendors-style.css

290 ms

style.css

289 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 42% of them (21 requests) were addressed to the original Todayville.com, 30% (15 requests) were made to Fonts.gstatic.com and 20% (10 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (449 ms) relates to the external source Fonts.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 568.9 kB (69%)

Content Size

828.8 kB

After Optimization

259.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Todayville.com main page is 828.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. HTML takes 613.2 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 566.7 kB

  • Original 613.2 kB
  • After minification 535.0 kB
  • After compression 46.5 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 78.2 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 566.7 kB or 92% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 55.1 kB
  • After minification 55.1 kB
  • After compression 55.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 2.2 kB

  • Original 160.5 kB
  • After minification 160.5 kB
  • After compression 158.3 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. Todayville.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (90%)

Requests Now

31

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

todayville.com

todayville.com

176 ms

www.todayville.com

www.todayville.com

287 ms

style.min.css

style.min.css

328 ms

vendors-style.css

vendors-style.css

290 ms

style.css

style.css

289 ms

6356cdde37f2373f8d1ff6b5118540fe.css

6356cdde37f2373f8d1ff6b5118540fe.css

233 ms

7747814c3baad9e776557df85e4f703e.css

7747814c3baad9e776557df85e4f703e.css

257 ms

1080d3b7c7e6f447bc02d496dbc0bcc9.css

1080d3b7c7e6f447bc02d496dbc0bcc9.css

278 ms

f38673e49f781b0c775ca972a0962d7f.css

f38673e49f781b0c775ca972a0962d7f.css

238 ms

css

css

402 ms

dashicons.min.css

dashicons.min.css

316 ms

69cd6ab5dfdef8741129634e7481ee6d.css

69cd6ab5dfdef8741129634e7481ee6d.css

254 ms

thickbox.css

thickbox.css

265 ms

woocommerce-layout.css

woocommerce-layout.css

313 ms

woocommerce.css

woocommerce.css

339 ms

a9a7ee8a86264e5d802a24445beb506f.css

a9a7ee8a86264e5d802a24445beb506f.css

254 ms

177bdf3ba8a78eb55d817827871af255.css

177bdf3ba8a78eb55d817827871af255.css

406 ms

f1d185d2a6e813b74c7ea401533cf9eb.css

f1d185d2a6e813b74c7ea401533cf9eb.css

381 ms

css

css

425 ms

aaf27b9a0d29ea33c39ec5d5ca17e731.css

aaf27b9a0d29ea33c39ec5d5ca17e731.css

368 ms

css

css

449 ms

5d44616ea2d6931381e5265963f84409.css

5d44616ea2d6931381e5265963f84409.css

383 ms

25ba78a54a9de819fe0ec01c1a836596.css

25ba78a54a9de819fe0ec01c1a836596.css

375 ms

c770cc46dd94a0fda1536f801e9d4b3d.css

c770cc46dd94a0fda1536f801e9d4b3d.css

403 ms

c328df196636bbd436e4b81c161101db.css

c328df196636bbd436e4b81c161101db.css

417 ms

ce9f6835d0a87b93520668c99718b64d.css

ce9f6835d0a87b93520668c99718b64d.css

415 ms

jetpack.css

jetpack.css

325 ms

todayville-red-deer.svg

todayville-red-deer.svg

343 ms

lazyload.min.js

lazyload.min.js

275 ms

rocket-loader.min.js

rocket-loader.min.js

258 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

50 ms

ea8a2da6dbc031d2834e011fb7cb4536.js

ea8a2da6dbc031d2834e011fb7cb4536.js

247 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

278 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

320 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

327 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

326 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

323 ms

weathericons-regular-webfont.woff

weathericons-regular-webfont.woff

42 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf

323 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

321 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

324 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

330 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

327 ms

evo_fontawesome-webfont.woff

evo_fontawesome-webfont.woff

165 ms

EJRVQgYoZZY2vCFuvAFWzro.ttf

EJRVQgYoZZY2vCFuvAFWzro.ttf

329 ms

EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf

EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf

331 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

324 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

326 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

323 ms

jquery.js

jquery.js

146 ms

SEO Factors

todayville.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Todayville.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 Todayville.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

todayville.com

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