Tools & Wizards About Us
fatfeet.com screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

Page Load Speed

2.2 sec in total

First Response

125 ms

Resources Loaded

1.8 sec

Page Rendered

214 ms

fatfeet.com screenshot

About Website

Welcome to fatfeet.com homepage info - get ready to check Fat Feet best content right away, or after learning these important things about fatfeet.com

Visit fatfeet.com

Key Findings

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

Performance Metrics

fatfeet.com performance score

0

Network Requests Diagram

www.fatfeet.com

125 ms

iframe_cm_18600

627 ms

hornybirds-160x600_3.jpg

81 ms

iframe_geobanner_300x250

740 ms

iframe_cm_22223

624 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fatfeet.com, 61% (27 requests) were made to Graphics.pop6.com and 7% (3 requests) were made to Banners.adultfriendfinder.com. The less responsive or slowest element that took the longest time to load (740 ms) relates to the external source Geobanner.adultfriendfinder.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.7 kB (20%)

Content Size

420.3 kB

After Optimization

335.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fatfeet.com main page is 420.3 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. 30% of websites need less resources to load. Images take 226.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 9.8 kB

  • Original 12.9 kB
  • After minification 11.8 kB
  • After compression 3.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 9.8 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 8.3 kB

  • Original 226.6 kB
  • After minification 218.3 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. Fat Feet images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 57.9 kB

  • Original 169.7 kB
  • After minification 169.3 kB
  • After compression 111.8 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 57.9 kB or 34% of the original size.

CSS Optimization

-78%

Potential reduce by 8.7 kB

  • Original 11.1 kB
  • After minification 9.6 kB
  • After compression 2.4 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. Fatfeet.com needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (9%)

Requests Now

43

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fatfeet.com

www.fatfeet.com

125 ms

iframe_cm_18600

iframe_cm_18600

627 ms

hornybirds-160x600_3.jpg

hornybirds-160x600_3.jpg

81 ms

iframe_geobanner_300x250

iframe_geobanner_300x250

740 ms

iframe_cm_22223

iframe_cm_22223

624 ms

momsbangteens-200x200_1.gif

momsbangteens-200x200_1.gif

72 ms

header.css

header.css

497 ms

density_map-1326143189.css

density_map-1326143189.css

503 ms

density_banner.cgi

density_banner.cgi

526 ms

ffadult-density_map-1328913018.js

ffadult-density_map-1328913018.js

503 ms

tgL6TnutaFXemKqOO52i7Q.jpg

tgL6TnutaFXemKqOO52i7Q.jpg

175 ms

logo.gif

logo.gif

100 ms

join.gif

join.gif

102 ms

findSingles.gif

findSingles.gif

100 ms

wm3CdHSCXtUS3Cc2JIrnpQ.jpg

wm3CdHSCXtUS3Cc2JIrnpQ.jpg

107 ms

piclist_profile2.png

piclist_profile2.png

106 ms

oKRbn5iTFla3b8aPRPUKuQ.jpg

oKRbn5iTFla3b8aPRPUKuQ.jpg

108 ms

fWzl9CDxCFyiZyqodBeSPQw.jpg

fWzl9CDxCFyiZyqodBeSPQw.jpg

107 ms

disclaimer.gif

disclaimer.gif

108 ms

logo.gif

logo.gif

108 ms

button.gif

button.gif

115 ms

density_banner.cgi

density_banner.cgi

554 ms

logo_medium.gif

logo_medium.gif

85 ms

bg_gradient.png

bg_gradient.png

85 ms

80007484_60320.26065003.gallery.gif

80007484_60320.26065003.gallery.gif

149 ms

_self.html

_self.html

155 ms

8Mx5egQmSVX2mcxNj0aoSPw.jpg

8Mx5egQmSVX2mcxNj0aoSPw.jpg

81 ms

Xq9ZaZHzoTxWIssJhSLTx8Q.jpg

Xq9ZaZHzoTxWIssJhSLTx8Q.jpg

75 ms

v2SLI9fitbjOjQtk2LyipSLA.jpg

v2SLI9fitbjOjQtk2LyipSLA.jpg

77 ms

f8epV86loSPVeerbpQOIMeg.jpg

f8epV86loSPVeerbpQOIMeg.jpg

75 ms

TbCqXYY3N3d70Sdw6PvT7A.jpg

TbCqXYY3N3d70Sdw6PvT7A.jpg

79 ms

med_shw.png

med_shw.png

77 ms

-77_39_4_17_6_1.js

-77_39_4_17_6_1.js

374 ms

SsKWPGJmSPDkGylMpZ0K3rA.jpg

SsKWPGJmSPDkGylMpZ0K3rA.jpg

26 ms

rrDBpyiT03B1S4Az6fIwRQ.jpg

rrDBpyiT03B1S4Az6fIwRQ.jpg

29 ms

_self.html

_self.html

74 ms

JSZl5y9svsVozlbfsXjqBg.jpg

JSZl5y9svsVozlbfsXjqBg.jpg

30 ms

NZtlM169pwIJXyKC4aiBMg.jpg

NZtlM169pwIJXyKC4aiBMg.jpg

27 ms

OEDMOF1t4vdCeJgUEBrVwg.jpg

OEDMOF1t4vdCeJgUEBrVwg.jpg

31 ms

1pSgtcN75KUdaNjdKAITcg.jpg

1pSgtcN75KUdaNjdKAITcg.jpg

27 ms

Mn9yY5QtBqZpHzPnc6SLKuA.jpg

Mn9yY5QtBqZpHzPnc6SLKuA.jpg

28 ms

XSP0jRpcdDIYF8g54TomnDw.jpg

XSP0jRpcdDIYF8g54TomnDw.jpg

50 ms

Wt0QYtkSP3k4LaYuL5g22VA.jpg

Wt0QYtkSP3k4LaYuL5g22VA.jpg

52 ms

-77_39_6_17_3_2.js

-77_39_6_17_3_2.js

213 ms

Accessibility Review

fatfeet.com accessibility score

33

Accessibility Issues

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

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

fatfeet.com best practices score

85

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

fatfeet.com SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fatfeet.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fatfeet.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

fatfeet.com

Open Graph description is not detected on the main page of Fat Feet. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: