Tools & Wizards About Us
christmasincolumbus.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

christmasincolumbus.com

93.3 The Bus - Columbus' Christmas Station

Page Load Speed

4 sec in total

First Response

1.8 sec

Resources Loaded

2.2 sec

Page Rendered

60 ms

christmasincolumbus.com screenshot

About Website

Visit christmasincolumbus.com now to see the best up-to-date Christmas In Columbus content and also check out these interesting facts you probably never knew about christmasincolumbus.com

Hits from the 70s, 80s & 90s

Visit christmasincolumbus.com

Key Findings

We analyzed Christmasincolumbus.com page load time and found that the first response time was 1.8 sec and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

christmasincolumbus.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value4,640 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.308

38/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

933odc.iheart.com

1758 ms

bundle.af116c1d41aebd831d9c.css

64 ms

local.bc06f128f534d4a5d747.css

60 ms

core-components-tiles-OnairTileLoader-component.12f62d6d6ad5771d626e.css

61 ms

core-page-blocks-datasource-DatasourceLoader-component.ed118ca85e0cefc658b6.css

69 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Christmasincolumbus.com, 4% (2 requests) were made to Z.moatads.com and 4% (2 requests) were made to I.iheart.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source 933odc.iheart.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 868.7 kB (53%)

Content Size

1.6 MB

After Optimization

768.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 688.5 kB

  • Original 850.2 kB
  • After minification 849.7 kB
  • After compression 161.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 688.5 kB or 81% of the original size.

Image Optimization

-14%

Potential reduce by 1.3 kB

  • Original 9.0 kB
  • After minification 7.7 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, Christmas In Columbus needs image optimization as it can save up to 1.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-24%

Potential reduce by 177.5 kB

  • Original 749.1 kB
  • After minification 749.1 kB
  • After compression 571.6 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 177.5 kB or 24% of the original size.

CSS Optimization

-5%

Potential reduce by 1.4 kB

  • Original 28.8 kB
  • After minification 28.7 kB
  • After compression 27.5 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. Christmasincolumbus.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (87%)

Requests Now

55

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

933odc.iheart.com

933odc.iheart.com

1758 ms

bundle.af116c1d41aebd831d9c.css

bundle.af116c1d41aebd831d9c.css

64 ms

local.bc06f128f534d4a5d747.css

local.bc06f128f534d4a5d747.css

60 ms

core-components-tiles-OnairTileLoader-component.12f62d6d6ad5771d626e.css

core-components-tiles-OnairTileLoader-component.12f62d6d6ad5771d626e.css

61 ms

core-page-blocks-datasource-DatasourceLoader-component.ed118ca85e0cefc658b6.css

core-page-blocks-datasource-DatasourceLoader-component.ed118ca85e0cefc658b6.css

69 ms

Datasource-component.a1eb25fbdc158e499608.css

Datasource-component.a1eb25fbdc158e499608.css

70 ms

Grid-component.9e05f3f8fa0e6b993347.css

Grid-component.9e05f3f8fa0e6b993347.css

68 ms

components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css

components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css

69 ms

core-page-blocks-music-MusicTile-component.c0f2337b7d57cb7e8b6d.css

core-page-blocks-music-MusicTile-component.c0f2337b7d57cb7e8b6d.css

69 ms

Heading-component.d79a5c95e6ef67a97bca.css

Heading-component.d79a5c95e6ef67a97bca.css

70 ms

LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css

LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css

71 ms

core-page-blocks-datasource-DatasourceTileLoader-component.a1eb25fbdc158e499608.css

core-page-blocks-datasource-DatasourceTileLoader-component.a1eb25fbdc158e499608.css

75 ms

FauxButton-component.1f25bb623660eb4f88c1.css

FauxButton-component.1f25bb623660eb4f88c1.css

71 ms

Eyebrow-component.23e83d8b8cab22ea99d6.css

Eyebrow-component.23e83d8b8cab22ea99d6.css

74 ms

Podcasts-component.570accd833088f4c4e7d.css

Podcasts-component.570accd833088f4c4e7d.css

72 ms

ImageTile-component.c2cbd469fbc0bd11cbdf.css

ImageTile-component.c2cbd469fbc0bd11cbdf.css

75 ms

Card-component.c66d212af09897afcdd6.css

Card-component.c66d212af09897afcdd6.css

79 ms

components-catalog-TrackList-component.626e2b289929900208bd.css

components-catalog-TrackList-component.626e2b289929900208bd.css

78 ms

AptivadaKeywordContest-component.a21f13419d9d48bf409a.css

AptivadaKeywordContest-component.a21f13419d9d48bf409a.css

75 ms

sdk.js

sdk.js

131 ms

moatheader.js

moatheader.js

131 ms

ebx.js

ebx.js

73 ms

runtime.cb66cc5e8cd4543b7929.js

runtime.cb66cc5e8cd4543b7929.js

66 ms

vendor.63f2f7bffa688d9d9622.js

vendor.63f2f7bffa688d9d9622.js

124 ms

bundle.2a3672ad9e244a3e76ed.js

bundle.2a3672ad9e244a3e76ed.js

181 ms

packages-renderer-shared-ui-src-elements-MagicLink-component.61532071211bf452d2ef.js

packages-renderer-shared-ui-src-elements-MagicLink-component.61532071211bf452d2ef.js

65 ms

src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_HeaderSearch_component_tsx-src_-b801d3.6041e11b8d0e121e52b7.js

src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_HeaderSearch_component_tsx-src_-b801d3.6041e11b8d0e121e52b7.js

121 ms

local.66ed3ba7b565dcbed23f.js

local.66ed3ba7b565dcbed23f.js

121 ms

core-components-tiles-OnairTileLoader-component.22fd96ce3a97461201e5.js

core-components-tiles-OnairTileLoader-component.22fd96ce3a97461201e5.js

122 ms

core-page-blocks-datasource-DatasourceLoader-component.f48ec165e3da9a949f55.js

core-page-blocks-datasource-DatasourceLoader-component.f48ec165e3da9a949f55.js

120 ms

packages_renderer_shared_core_src_lib_ads_ts.b42bd2acb8a91fae3845.js

packages_renderer_shared_core_src_lib_ads_ts.b42bd2acb8a91fae3845.js

123 ms

Datasource-component.1423c7d635806130822c.js

Datasource-component.1423c7d635806130822c.js

121 ms

Grid-component.48dae21730bceb9ee5e7.js

Grid-component.48dae21730bceb9ee5e7.js

165 ms

ContentFeedItem-component.a58f9b17ed1802cd6512.js

ContentFeedItem-component.a58f9b17ed1802cd6512.js

123 ms

LeadFeedItem-component.f9b025ed7a795a039e16.js

LeadFeedItem-component.f9b025ed7a795a039e16.js

166 ms

components-tiles-ContentTile-component.8fe9a91f6ecd8ec889d2.js

components-tiles-ContentTile-component.8fe9a91f6ecd8ec889d2.js

165 ms

core-page-blocks-music-MusicTile-component.ee3234ca914dd952a1c0.js

core-page-blocks-music-MusicTile-component.ee3234ca914dd952a1c0.js

166 ms

core-page-blocks-podcast-PodcastsLoader-component.c847d80e9aa862b03d51.js

core-page-blocks-podcast-PodcastsLoader-component.c847d80e9aa862b03d51.js

166 ms

Heading-component.ea88c81b8d34c977158c.js

Heading-component.ea88c81b8d34c977158c.js

167 ms

LoadMoreFromCursor-component.bb890d9dab9374f42e37.js

LoadMoreFromCursor-component.bb890d9dab9374f42e37.js

167 ms

core-page-blocks-datasource-DatasourceTileLoader-component.05d77890dc9884cc76e2.js

core-page-blocks-datasource-DatasourceTileLoader-component.05d77890dc9884cc76e2.js

128 ms

FauxButton-component.6f17f4f82d52801c5c49.js

FauxButton-component.6f17f4f82d52801c5c49.js

127 ms

core-page-blocks-contest-KeywordContestLoader-component.5e0cc4120d526a5ea860.js

core-page-blocks-contest-KeywordContestLoader-component.5e0cc4120d526a5ea860.js

127 ms

Eyebrow-component.533482f1ba2c4fcd4202.js

Eyebrow-component.533482f1ba2c4fcd4202.js

124 ms

vendors-node_modules_pnpm_isomorphic-dompurify_0_27_0_node_modules_isomorphic-dompurify_browser_js.05cdd4f29edec5e3d7e3.js

vendors-node_modules_pnpm_isomorphic-dompurify_0_27_0_node_modules_isomorphic-dompurify_browser_js.05cdd4f29edec5e3d7e3.js

121 ms

Podcasts-component.ab2989f0ebc0ae9ef4c1.js

Podcasts-component.ab2989f0ebc0ae9ef4c1.js

122 ms

ImageTile-component.b3ff14a77346457b64fe.js

ImageTile-component.b3ff14a77346457b64fe.js

121 ms

Card-component.24dee8840408569eb2c3.js

Card-component.24dee8840408569eb2c3.js

122 ms

components-catalog-TrackList-component.644cdb9aaf258f95a9d3.js

components-catalog-TrackList-component.644cdb9aaf258f95a9d3.js

122 ms

DateTimeDisplay-component.a955bfacd3eb846a09d1.js

DateTimeDisplay-component.a955bfacd3eb846a09d1.js

121 ms

AptivadaKeywordContest-component.d932ebf2afeb78ef5324.js

AptivadaKeywordContest-component.d932ebf2afeb78ef5324.js

123 ms

63ab478d7dcb60ce00b65591

63ab478d7dcb60ce00b65591

222 ms

f79fc341-a979-4863-81b0-eea1ddc6e07b

f79fc341-a979-4863-81b0-eea1ddc6e07b

93 ms

v2

v2

72 ms

n.js

n.js

67 ms

iframe.html

iframe.html

11 ms

Accessibility Review

christmasincolumbus.com accessibility score

100

Accessibility Issues

Best Practices

christmasincolumbus.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

christmasincolumbus.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Christmasincolumbus.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 Christmasincolumbus.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

christmasincolumbus.com

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