Tools & Wizards About Us
fateyes.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

fateyes.com

Santa Barbara Web Design & Santa Barbara Web Development: Fat Eyes

Page Load Speed

2.8 sec in total

First Response

502 ms

Resources Loaded

1.9 sec

Page Rendered

376 ms

fateyes.com screenshot

About Website

Welcome to fateyes.com homepage info - get ready to check Fat Eyes best content for United States right away, or after learning these important things about fateyes.com

Best customer service since 1998 for Santa Barbara Web Design & Santa Barbara Web Development. WordPress for Business, Ecommerce & Non-profits, SEO, Mobile

Visit fateyes.com

Key Findings

We analyzed Fateyes.com page load time and found that the first response time was 502 ms and then it took 2.3 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

fateyes.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value1,470 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

www.fateyes.com

502 ms

test.css

37 ms

styles.css

61 ms

style.css

148 ms

front.css

89 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 88% of them (72 requests) were addressed to the original Fateyes.com, 4% (3 requests) were made to Static.olark.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (502 ms) belongs to the original domain Fateyes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 496.4 kB (32%)

Content Size

1.5 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 55.1 kB

  • Original 70.3 kB
  • After minification 68.2 kB
  • After compression 15.2 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 55.1 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 81.1 kB

  • Original 949.6 kB
  • After minification 868.5 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 Eyes images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 244.6 kB

  • Original 371.5 kB
  • After minification 347.7 kB
  • After compression 126.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 244.6 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 115.6 kB

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

Requests Breakdown

Number of requests can be reduced by 37 (46%)

Requests Now

81

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fateyes.com

www.fateyes.com

502 ms

test.css

test.css

37 ms

styles.css

styles.css

61 ms

style.css

style.css

148 ms

front.css

front.css

89 ms

plugin.styles.css

plugin.styles.css

61 ms

awp-columns.css

awp-columns.css

74 ms

jquery.fancybox-1.3.7.min.css

jquery.fancybox-1.3.7.min.css

103 ms

jquery.js

jquery.js

158 ms

jquery-migrate.min.js

jquery-migrate.min.js

132 ms

include.js

include.js

185 ms

script.min.js

script.min.js

187 ms

script.js

script.js

184 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

196 ms

shailan-dropdown.min.css

shailan-dropdown.min.css

218 ms

mediaqueries.css

mediaqueries.css

213 ms

meanmenu.css

meanmenu.css

211 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

229 ms

jquery.meanmenu.js

jquery.meanmenu.js

225 ms

jquery.placeholder.js

jquery.placeholder.js

224 ms

plugin.css

plugin.css

226 ms

flexslider.css

flexslider.css

309 ms

public.css

public.css

309 ms

hoverIntent.min.js

hoverIntent.min.js

315 ms

core.min.js

core.min.js

314 ms

widget.min.js

widget.min.js

316 ms

tabs.min.js

tabs.min.js

342 ms

comment-reply.min.js

comment-reply.min.js

342 ms

wp-embed.min.js

wp-embed.min.js

345 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

354 ms

jquery.fancybox-1.3.7.min.js

jquery.fancybox-1.3.7.min.js

357 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

394 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

351 ms

bg-top-left-corner.jpg

bg-top-left-corner.jpg

156 ms

bg-top.jpg

bg-top.jpg

162 ms

logo.png

logo.png

162 ms

menuborder.png

menuborder.png

201 ms

blank.png

blank.png

198 ms

sub-menu-bg.png

sub-menu-bg.png

200 ms

bg-top-right-corner.jpg

bg-top-right-corner.jpg

202 ms

bg-left.jpg

bg-left.jpg

223 ms

timthumb-1.jpg

timthumb-1.jpg

241 ms

timthumb-2.jpg

timthumb-2.jpg

242 ms

timthumb-3.jpg

timthumb-3.jpg

222 ms

timthumb-4.jpg

timthumb-4.jpg

287 ms

timthumb-5.jpg

timthumb-5.jpg

282 ms

timthumb-8.jpg

timthumb-8.jpg

288 ms

timthumb.jpg

timthumb.jpg

491 ms

bienNacidoVineyards-618x264.jpg

bienNacidoVineyards-618x264.jpg

493 ms

casaDelHerrero-618x264.jpg

casaDelHerrero-618x264.jpg

491 ms

cultureCrossing-618x264.jpg

cultureCrossing-618x264.jpg

493 ms

eDC-618x264.jpg

eDC-618x264.jpg

496 ms

hirschVineyards-618x264.jpg

hirschVineyards-618x264.jpg

491 ms

losOlivosCafe-618x264.jpg

losOlivosCafe-618x264.jpg

496 ms

melis-618x264.jpg

melis-618x264.jpg

496 ms

nsCeramic-618x264.jpg

nsCeramic-618x264.jpg

495 ms

pancan-618x264.jpg

pancan-618x264.jpg

487 ms

ps_2-webfont.woff

ps_2-webfont.woff

438 ms

underdogMedia-618x264.jpg

underdogMedia-618x264.jpg

479 ms

facebook2Black1.png

facebook2Black1.png

477 ms

linkedInBlack.png

linkedInBlack.png

473 ms

lsans-webfont.woff

lsans-webfont.woff

467 ms

loader0.js

loader0.js

102 ms

agaramondpro-bolditalic-webfont.woff

agaramondpro-bolditalic-webfont.woff

449 ms

bg-left-corner.jpg

bg-left-corner.jpg

447 ms

sw-icon-font.woff

sw-icon-font.woff

448 ms

like.php

like.php

129 ms

bg-right-corner.jpg

bg-right-corner.jpg

435 ms

ga.js

ga.js

44 ms

css

css

114 ms

reviewourportfolio-bg.png

reviewourportfolio-bg.png

443 ms

topmenu-icon.jpg

topmenu-icon.jpg

422 ms

footer-border.png

footer-border.png

424 ms

bg-right.jpg

bg-right.jpg

421 ms

bg-bottom.jpg

bg-bottom.jpg

418 ms

__utm.gif

__utm.gif

31 ms

4178-721-10-7150.js

4178-721-10-7150.js

287 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

432 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

471 ms

c

c

104 ms

bg_direction_nav.png

bg_direction_nav.png

37 ms

application2.js

application2.js

136 ms

Accessibility Review

fateyes.com accessibility score

94

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-hidden="true"] elements contain focusable descendents

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.

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

fateyes.com SEO score

100

Search Engine Optimization Advices

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

fateyes.com

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