Tools & Wizards About Us
faemasource.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

faemasource.com

FaemaSource | The easy way to find the right Faema parts

Page Load Speed

7.9 sec in total

First Response

81 ms

Resources Loaded

7.3 sec

Page Rendered

537 ms

faemasource.com screenshot

About Website

Click here to check amazing Faema Source content. Otherwise, check out these important facts you probably never knew about faemasource.com

With our expertise of Faema machines and our huge inventory of parts, we aim to get your machine running in no time. Call us and we will help you find the right parts Phone: (877) 335 2766

Visit faemasource.com

Key Findings

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

Performance Metrics

faemasource.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

faemasource.com

81 ms

www.faemasource.com

180 ms

js

64 ms

bootstrap.min.css

112 ms

style.css

143 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 54% of them (48 requests) were addressed to the original Faemasource.com, 34% (30 requests) were made to Static.cdninstagram.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.9 sec) relates to the external source Via.placeholder.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 605.8 kB (18%)

Content Size

3.4 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Faemasource.com main page is 3.4 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. 75% 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.9 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 43.3 kB

  • Original 49.9 kB
  • After minification 33.5 kB
  • After compression 6.6 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. This page needs HTML code to be minified as it can gain 16.3 kB, which is 33% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.3 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 160.5 kB

  • Original 2.9 MB
  • After minification 2.7 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. Faema Source images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 158.6 kB

  • Original 214.2 kB
  • After minification 183.5 kB
  • After compression 55.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 158.6 kB or 74% of the original size.

CSS Optimization

-84%

Potential reduce by 243.5 kB

  • Original 291.2 kB
  • After minification 266.9 kB
  • After compression 47.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. Faemasource.com needs all CSS files to be minified and compressed as it can save up to 243.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (53%)

Requests Now

74

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

faemasource.com

faemasource.com

81 ms

www.faemasource.com

www.faemasource.com

180 ms

js

js

64 ms

bootstrap.min.css

bootstrap.min.css

112 ms

style.css

style.css

143 ms

owl.carousel.css

owl.carousel.css

76 ms

font-awesome.css

font-awesome.css

116 ms

font-awesome.min.css

font-awesome.min.css

106 ms

css

css

39 ms

logo.png

logo.png

123 ms

1920x900_barista1.jpg

1920x900_barista1.jpg

669 ms

e61.jpg

e61.jpg

770 ms

enova.jpg

enova.jpg

164 ms

granditalia.jpg

granditalia.jpg

183 ms

515x468.jpg

515x468.jpg

385 ms

385x338

385x338

77 ms

3851.jpg

3851.jpg

736 ms

3852.jpg

3852.jpg

170 ms

3853.jpg

3853.jpg

271 ms

38534.jpg

38534.jpg

412 ms

38535.jpg

38535.jpg

350 ms

38536.jpg

38536.jpg

439 ms

38537.jpg

38537.jpg

462 ms

38538.jpg

38538.jpg

539 ms

38539.jpg

38539.jpg

529 ms

385310.jpg

385310.jpg

585 ms

385x338

385x338

1 ms

bud.jpg

bud.jpg

122 ms

jeremy.jpg

jeremy.jpg

121 ms

embed.js

embed.js

84 ms

jquery.min.js

jquery.min.js

582 ms

bootstrap.min.js

bootstrap.min.js

556 ms

owl.carousel.js

owl.carousel.js

610 ms

custom.js

custom.js

595 ms

370x237-1.jpg

370x237-1.jpg

654 ms

370x237-2.jpg

370x237-2.jpg

691 ms

370x237-3.jpg

370x237-3.jpg

699 ms

patner-11.png

patner-11.png

647 ms

patner-12.png

patner-12.png

665 ms

patner-13.png

patner-13.png

672 ms

partner-16.png

partner-16.png

684 ms

partner-15.png

partner-15.png

691 ms

385x338

385x338

6939 ms

bg-setting.png

bg-setting.png

603 ms

img3.jpg

img3.jpg

609 ms

icon-tols.png

icon-tols.png

592 ms

img5.jpg

img5.jpg

968 ms

bud.jpg

bud.jpg

793 ms

jeremy.jpg

jeremy.jpg

869 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

839 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

809 ms

opensans-semibold-webfont.woff

opensans-semibold-webfont.woff

605 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

867 ms

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf

15 ms

tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTQ.ttf

tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTQ.ttf

20 ms

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

30 ms

tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf

tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf

30 ms

opensans-light-webfont.woff

opensans-light-webfont.woff

733 ms

214 ms

sqiLHmuCKjb.css

sqiLHmuCKjb.css

25 ms

3z7cqs7Ks6-.css

3z7cqs7Ks6-.css

49 ms

d92nukCtz1l.css

d92nukCtz1l.css

58 ms

RXhBbhZmneD.css

RXhBbhZmneD.css

67 ms

L-_NjDlvXrA.js

L-_NjDlvXrA.js

81 ms

szSrDf3yAfN.js

szSrDf3yAfN.js

8 ms

YwyE45LTAN1.js

YwyE45LTAN1.js

8 ms

MS7A52kJp6_.js

MS7A52kJp6_.js

7 ms

tZOq-l13ojS.js

tZOq-l13ojS.js

7 ms

qU1o16FN1Jt.js

qU1o16FN1Jt.js

28 ms

jKz083MCCVo.js

jKz083MCCVo.js

28 ms

4HyKR-TfEWR.js

4HyKR-TfEWR.js

28 ms

lNInKxOqejp.js

lNInKxOqejp.js

28 ms

5fX-Po9j9H3.js

5fX-Po9j9H3.js

27 ms

GJ_1fTPMh38.js

GJ_1fTPMh38.js

45 ms

tuae-GO5w2L.js

tuae-GO5w2L.js

45 ms

db_RQLQYjko.js

db_RQLQYjko.js

43 ms

6yNgW0PF5p3.js

6yNgW0PF5p3.js

44 ms

vflPqbCGAJj.js

vflPqbCGAJj.js

45 ms

Gif8tU2ZVrl.js

Gif8tU2ZVrl.js

44 ms

cBmLqZhej__.js

cBmLqZhej__.js

46 ms

-muIeYlBGQh.js

-muIeYlBGQh.js

47 ms

GhZEvSLVF3e.js

GhZEvSLVF3e.js

45 ms

UDFCsXtDquD.js

UDFCsXtDquD.js

47 ms

ylyTmy7Tpht.js

ylyTmy7Tpht.js

46 ms

-7SoqkOoiBI.js

-7SoqkOoiBI.js

46 ms

R8ZTLxqI2uK.js

R8ZTLxqI2uK.js

48 ms

OdRoWSPknPK.js

OdRoWSPknPK.js

49 ms

dyyaOZ5_Vv4.js

dyyaOZ5_Vv4.js

49 ms

wFyxcb5a_CA.png

wFyxcb5a_CA.png

48 ms

Accessibility Review

faemasource.com accessibility score

84

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

faemasource.com SEO score

97

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

High

Tap targets are not sized appropriately

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

faemasource.com

Open Graph description is not detected on the main page of Faema Source. 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: