2.8 sec in total
502 ms
1.9 sec
376 ms
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.comWe 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.
fateyes.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value8.0 s
2/100
25%
Value5.0 s
63/100
10%
Value1,470 ms
14/100
30%
Value0
100/100
15%
Value11.5 s
18/100
10%
502 ms
37 ms
61 ms
148 ms
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 size can be reduced by 496.4 kB (32%)
1.5 MB
1.0 MB
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.
Potential reduce by 55.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 55.1 kB or 78% of the original size.
Potential reduce by 81.1 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.
Potential reduce by 244.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 244.6 kB or 66% of the original size.
Potential reduce by 115.6 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.
Number of requests can be reduced by 37 (46%)
81
44
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.
www.fateyes.com
502 ms
test.css
37 ms
styles.css
61 ms
style.css
148 ms
front.css
89 ms
plugin.styles.css
61 ms
awp-columns.css
74 ms
jquery.fancybox-1.3.7.min.css
103 ms
jquery.js
158 ms
jquery-migrate.min.js
132 ms
include.js
185 ms
script.min.js
187 ms
script.js
184 ms
AC_RunActiveContent.js
196 ms
shailan-dropdown.min.css
218 ms
mediaqueries.css
213 ms
meanmenu.css
211 ms
jquery-1.7.2.min.js
229 ms
jquery.meanmenu.js
225 ms
jquery.placeholder.js
224 ms
plugin.css
226 ms
flexslider.css
309 ms
public.css
309 ms
hoverIntent.min.js
315 ms
core.min.js
314 ms
widget.min.js
316 ms
tabs.min.js
342 ms
comment-reply.min.js
342 ms
wp-embed.min.js
345 ms
jquery.flexslider-min.js
354 ms
jquery.fancybox-1.3.7.min.js
357 ms
jquery.mousewheel.min.js
394 ms
wp-emoji-release.min.js
351 ms
bg-top-left-corner.jpg
156 ms
bg-top.jpg
162 ms
logo.png
162 ms
menuborder.png
201 ms
blank.png
198 ms
sub-menu-bg.png
200 ms
bg-top-right-corner.jpg
202 ms
bg-left.jpg
223 ms
timthumb-1.jpg
241 ms
timthumb-2.jpg
242 ms
timthumb-3.jpg
222 ms
timthumb-4.jpg
287 ms
timthumb-5.jpg
282 ms
timthumb-8.jpg
288 ms
timthumb.jpg
491 ms
bienNacidoVineyards-618x264.jpg
493 ms
casaDelHerrero-618x264.jpg
491 ms
cultureCrossing-618x264.jpg
493 ms
eDC-618x264.jpg
496 ms
hirschVineyards-618x264.jpg
491 ms
losOlivosCafe-618x264.jpg
496 ms
melis-618x264.jpg
496 ms
nsCeramic-618x264.jpg
495 ms
pancan-618x264.jpg
487 ms
ps_2-webfont.woff
438 ms
underdogMedia-618x264.jpg
479 ms
facebook2Black1.png
477 ms
linkedInBlack.png
473 ms
lsans-webfont.woff
467 ms
loader0.js
102 ms
agaramondpro-bolditalic-webfont.woff
449 ms
bg-left-corner.jpg
447 ms
sw-icon-font.woff
448 ms
like.php
129 ms
bg-right-corner.jpg
435 ms
ga.js
44 ms
css
114 ms
reviewourportfolio-bg.png
443 ms
topmenu-icon.jpg
422 ms
footer-border.png
424 ms
bg-right.jpg
421 ms
bg-bottom.jpg
418 ms
__utm.gif
31 ms
4178-721-10-7150.js
287 ms
qeKvIRsJabD.js
432 ms
LVx-xkvaJ0b.png
471 ms
c
104 ms
bg_direction_nav.png
37 ms
application2.js
136 ms
fateyes.com accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
fateyes.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fateyes.com SEO score
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
Document uses legible font sizes
EN
EN
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.
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: