Tools & Wizards About Us
songhenge.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

songhenge.com

Irish & Celtic Music Podcast | creating Podcasts | Patreon

Page Load Speed

3.3 sec in total

First Response

29 ms

Resources Loaded

3.2 sec

Page Rendered

76 ms

songhenge.com screenshot

About Website

Click here to check amazing Songhenge content. Otherwise, check out these important facts you probably never knew about songhenge.com

creating Podcasts

Visit songhenge.com

Key Findings

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

Performance Metrics

songhenge.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value20.0 s

0/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value6,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value39.3 s

0/100

10%

Network Requests Diagram

songhenge.com

29 ms

celticpodcast

2055 ms

celticpodcast

545 ms

polyfills-c67a75d1b6f99dc8.js

85 ms

airgap.js

106 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Songhenge.com, 78% (59 requests) were made to C13.patreon.com and 8% (6 requests) were made to C10.patreonusercontent.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Patreon.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 228.9 kB (8%)

Content Size

2.8 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Songhenge.com main page is 2.8 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. 60% of websites need less resources to load. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 227.0 kB

  • Original 304.1 kB
  • After minification 303.9 kB
  • After compression 77.1 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 227.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 500.6 kB
  • After minification 500.6 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. Songhenge images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.9 kB

  • Original 2.0 MB
  • After minification 2.0 MB
  • After compression 2.0 MB

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.

Requests Breakdown

Number of requests can be reduced by 65 (89%)

Requests Now

73

After Optimization

8

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

songhenge.com

songhenge.com

29 ms

celticpodcast

celticpodcast

2055 ms

celticpodcast

celticpodcast

545 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

85 ms

airgap.js

airgap.js

106 ms

api:client.js

api:client.js

64 ms

client

client

110 ms

appleid.auth.js

appleid.auth.js

160 ms

webpack-373d0978e6620255.js

webpack-373d0978e6620255.js

115 ms

framework-5b4b4bd7d64ffcfa.js

framework-5b4b4bd7d64ffcfa.js

156 ms

main-bba07c0d56e4f500.js

main-bba07c0d56e4f500.js

157 ms

_app-912f5e0f0dd97f23.js

_app-912f5e0f0dd97f23.js

262 ms

2852872c-657a224261f762b2.js

2852872c-657a224261f762b2.js

157 ms

37a763b4-eaaabd946be5e1fa.js

37a763b4-eaaabd946be5e1fa.js

166 ms

8b11cd73-f09294707b04d014.js

8b11cd73-f09294707b04d014.js

155 ms

f9afc4fe-6059a26458ac411b.js

f9afc4fe-6059a26458ac411b.js

182 ms

30381-6e8e8def86fca9d9.js

30381-6e8e8def86fca9d9.js

199 ms

91036-75f9a70fd050d3a3.js

91036-75f9a70fd050d3a3.js

197 ms

48764-06bfc6b2309ec52a.js

48764-06bfc6b2309ec52a.js

177 ms

58588-e0e06435aa683efe.js

58588-e0e06435aa683efe.js

185 ms

62609-a0237954904514ec.js

62609-a0237954904514ec.js

201 ms

28747-2563ab9829a8cb5f.js

28747-2563ab9829a8cb5f.js

203 ms

12066-7e608afc9da52563.js

12066-7e608afc9da52563.js

213 ms

64130-c52ecf2348ecd1c4.js

64130-c52ecf2348ecd1c4.js

220 ms

39174-278290511207d4fc.js

39174-278290511207d4fc.js

226 ms

94232-fc737e543b5862b2.js

94232-fc737e543b5862b2.js

224 ms

58234-108becf07df07eea.js

58234-108becf07df07eea.js

226 ms

63614-47d14af560f6497d.js

63614-47d14af560f6497d.js

232 ms

66939-53957fd70b39ae4e.js

66939-53957fd70b39ae4e.js

255 ms

60600-6a46de53cf9e3c9b.js

60600-6a46de53cf9e3c9b.js

255 ms

86492-9e3ab8b68bbc8e7b.js

86492-9e3ab8b68bbc8e7b.js

282 ms

53415-b89e7e49bf0850fa.js

53415-b89e7e49bf0850fa.js

256 ms

40065-11e132ba9853a0b2.js

40065-11e132ba9853a0b2.js

284 ms

15979-c6f9368ddce0477c.js

15979-c6f9368ddce0477c.js

286 ms

35353-dd615ecdc086ed0f.js

35353-dd615ecdc086ed0f.js

287 ms

74105-117c4053b8492764.js

74105-117c4053b8492764.js

287 ms

89019-77c2a2cd5bc624d5.js

89019-77c2a2cd5bc624d5.js

290 ms

87326-e4431b9616d81e65.js

87326-e4431b9616d81e65.js

287 ms

2394-1329171cf11eafbb.js

2394-1329171cf11eafbb.js

287 ms

60306-a00da3ef4a243fb6.js

60306-a00da3ef4a243fb6.js

289 ms

9980-839d218b726e19bc.js

9980-839d218b726e19bc.js

288 ms

31772-7e19941aed7ded96.js

31772-7e19941aed7ded96.js

297 ms

54988-ba4dd9ece7cbbbcb.js

54988-ba4dd9ece7cbbbcb.js

298 ms

3.jpeg

3.jpeg

318 ms

shim.js

shim.js

42 ms

1.jpeg

1.jpeg

472 ms

1.jpeg

1.jpeg

440 ms

1.jpeg

1.jpeg

417 ms

1.jpg

1.jpg

350 ms

1.jpeg

1.jpeg

424 ms

assignments

assignments

493 ms

4599-28639dbd0e37115a.js

4599-28639dbd0e37115a.js

220 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

27779-141e969ec4581b73.js

27779-141e969ec4581b73.js

198 ms

38135-ccf13bbcb582fbe0.js

38135-ccf13bbcb582fbe0.js

166 ms

67244-a94f63e343e7ff23.js

67244-a94f63e343e7ff23.js

160 ms

5285-b9d4c5af1bf7dea2.js

5285-b9d4c5af1bf7dea2.js

174 ms

45408-00b45bc45a33fa07.js

45408-00b45bc45a33fa07.js

172 ms

74471-76e244aacf927ffb.js

74471-76e244aacf927ffb.js

170 ms

83761-09276853cfee4d45.js

83761-09276853cfee4d45.js

169 ms

20139-b05e22600c16ebf0.js

20139-b05e22600c16ebf0.js

186 ms

5792-a5d4c2e060adb84d.js

5792-a5d4c2e060adb84d.js

157 ms

77026-1c04d3ed796e319e.js

77026-1c04d3ed796e319e.js

151 ms

72070-dd8283369b5f5dde.js

72070-dd8283369b5f5dde.js

152 ms

95799-0ff8655e27c554a8.js

95799-0ff8655e27c554a8.js

182 ms

42719-39a5740e6e0cbe3c.js

42719-39a5740e6e0cbe3c.js

167 ms

48284-3f0470674d405c1c.js

48284-3f0470674d405c1c.js

158 ms

32395-849d23468ab733c3.js

32395-849d23468ab733c3.js

156 ms

17-2b1da49fe5b0d181.js

17-2b1da49fe5b0d181.js

149 ms

87960-a8ad66772bfdc37d.js

87960-a8ad66772bfdc37d.js

167 ms

1245-eb5eb2d87360ee0d.js

1245-eb5eb2d87360ee0d.js

161 ms

31338-3c79d992bc157c41.js

31338-3c79d992bc157c41.js

166 ms

%5B%5B...tab%5D%5D-926aa2864416998a.js

%5B%5B...tab%5D%5D-926aa2864416998a.js

136 ms

_buildManifest.js

_buildManifest.js

138 ms

_ssgManifest.js

_ssgManifest.js

121 ms

s.js

s.js

75 ms

Accessibility Review

songhenge.com accessibility score

63

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

songhenge.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

songhenge.com SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Songhenge.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Songhenge.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

songhenge.com

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