Tools & Wizards About Us
fannyhatstand.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fannyhatstand.com

Fanny Hatstand

Page Load Speed

6.5 sec in total

First Response

341 ms

Resources Loaded

2.3 sec

Page Rendered

3.9 sec

fannyhatstand.com screenshot

About Website

Click here to check amazing Fanny Hatstand content. Otherwise, check out these important facts you probably never knew about fannyhatstand.com

Fanny Hatstand is dedicated to promoting high quality original live music and events. Fanny's operation is master-minded from her secret headquarters somewhere in Somerset.

Visit fannyhatstand.com

Key Findings

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

Performance Metrics

fannyhatstand.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

88/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

fannyhatstand.com

341 ms

pre_tumblelog.js

8 ms

tumblelog_post_message_queue.js

14 ms

stylesheet.css

13 ms

all.js

723 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fannyhatstand.com, 22% (15 requests) were made to Youtube.com and 12% (8 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Gordonlangley.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 791.5 kB (23%)

Content Size

3.5 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fannyhatstand.com main page is 3.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 42.7 kB

  • Original 58.1 kB
  • After minification 55.0 kB
  • After compression 15.4 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 42.7 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 60.0 kB

  • Original 2.5 MB
  • After minification 2.4 MB

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. Fanny Hatstand images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 485.7 kB

  • Original 747.6 kB
  • After minification 747.5 kB
  • After compression 261.9 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 485.7 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 203.0 kB

  • Original 244.8 kB
  • After minification 244.8 kB
  • After compression 41.8 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. Fannyhatstand.com needs all CSS files to be minified and compressed as it can save up to 203.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (31%)

Requests Now

64

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fannyhatstand.com

fannyhatstand.com

341 ms

pre_tumblelog.js

pre_tumblelog.js

8 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

14 ms

stylesheet.css

stylesheet.css

13 ms

all.js

all.js

723 ms

index.js

index.js

48 ms

ga.js

ga.js

39 ms

paper.jpg

paper.jpg

1639 ms

tumblr_inline_o3doak3e781qg2e3i_500.jpg

tumblr_inline_o3doak3e781qg2e3i_500.jpg

868 ms

XODX_zjPy4Y

XODX_zjPy4Y

138 ms

tumblr_inline_o28f6uFwp61qg2e3i_500.jpg

tumblr_inline_o28f6uFwp61qg2e3i_500.jpg

626 ms

nvgNSxas9ZQ

nvgNSxas9ZQ

132 ms

o1ImcrzNyNI

o1ImcrzNyNI

121 ms

aB4MUjKUU-0

aB4MUjKUU-0

141 ms

YRNh4H37tPo

YRNh4H37tPo

143 ms

R60uKIzSNGk

R60uKIzSNGk

139 ms

tumblr_inline_nxek1rGtpI1qg2e3i_500.jpg

tumblr_inline_nxek1rGtpI1qg2e3i_500.jpg

73 ms

Z957sjiIVIs

Z957sjiIVIs

217 ms

F0st2F6Lg-o

F0st2F6Lg-o

225 ms

8MzL4jmKIpA

8MzL4jmKIpA

234 ms

aPJXDPkrWEY

aPJXDPkrWEY

242 ms

Lys-dFxnDpY

Lys-dFxnDpY

250 ms

5pqnk4TntGg

5pqnk4TntGg

529 ms

fCU66XmmoBg

fCU66XmmoBg

630 ms

vd89xRZ8XcI

vd89xRZ8XcI

605 ms

Pw5xvvCq-dk

Pw5xvvCq-dk

686 ms

tumblr_inline_njvifpGatl1qg2e3i.jpg

tumblr_inline_njvifpGatl1qg2e3i.jpg

580 ms

tumblr_inline_nhnx50hyga1qg2e3i.jpg

tumblr_inline_nhnx50hyga1qg2e3i.jpg

51 ms

tumblr_inline_o1awpd90Az1qg2e3i_500.jpg

tumblr_inline_o1awpd90Az1qg2e3i_500.jpg

708 ms

tumblr_inline_o1awqpRaqw1qg2e3i_500.jpg

tumblr_inline_o1awqpRaqw1qg2e3i_500.jpg

746 ms

tumblr_inline_nx5dtrgFKS1qg2e3i_500.jpg

tumblr_inline_nx5dtrgFKS1qg2e3i_500.jpg

708 ms

tumblr_inline_no173auWW81qg2e3i_400.jpg

tumblr_inline_no173auWW81qg2e3i_400.jpg

709 ms

tumblr_inline_nvn2mvUFBd1qg2e3i_500.jpg

tumblr_inline_nvn2mvUFBd1qg2e3i_500.jpg

189 ms

tumblr_inline_nnq7h3AVIN1qg2e3i_500.jpg

tumblr_inline_nnq7h3AVIN1qg2e3i_500.jpg

620 ms

tumblr_inline_nhurczRfBO1qg2e3i.jpg

tumblr_inline_nhurczRfBO1qg2e3i.jpg

707 ms

fanny-hatstand.png

fanny-hatstand.png

1186 ms

tumblr_inline_nvn2g5iPRs1qg2e3i_500.jpg

tumblr_inline_nvn2g5iPRs1qg2e3i_500.jpg

619 ms

tumblr_inline_nvn4q7ESri1qg2e3i_500.jpg

tumblr_inline_nvn4q7ESri1qg2e3i_500.jpg

53 ms

tumblr_inline_ntg4yisiyc1qg2e3i_500.jpg

tumblr_inline_ntg4yisiyc1qg2e3i_500.jpg

53 ms

__utm.gif

__utm.gif

16 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

30 ms

www-embed-player.js

www-embed-player.js

58 ms

base.js

base.js

145 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

400 ms

ad_status.js

ad_status.js

400 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

198 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

198 ms

529 ms

xd_arbiter.php

xd_arbiter.php

451 ms

xd_arbiter.php

xd_arbiter.php

714 ms

impixu

impixu

445 ms

impixu

impixu

359 ms

analytics.html

analytics.html

354 ms

login_check.html

login_check.html

76 ms

like.php

like.php

207 ms

rapid-3.36.js

rapid-3.36.js

194 ms

rapidworker-1.2.js

rapidworker-1.2.js

197 ms

iframe_logo.png

iframe_logo.png

55 ms

avatar_ec140f69fe8f_40.png

avatar_ec140f69fe8f_40.png

59 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

498 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

553 ms

ga.js

ga.js

86 ms

analytics.js

analytics.js

74 ms

cs.js

cs.js

85 ms

yql

yql

194 ms

__utm.gif

__utm.gif

17 ms

cedexis.radar.js

cedexis.radar.js

5 ms

Accessibility Review

fannyhatstand.com accessibility score

52

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

fannyhatstand.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fannyhatstand.com SEO score

86

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

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 Fannyhatstand.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 Fannyhatstand.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

fannyhatstand.com

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