Tools & Wizards About Us
fawn.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

fawn.com

Fawn Industries, Custom Embroidery - New Park, PA (800) 388-FAWN

Page Load Speed

1.8 sec in total

First Response

133 ms

Resources Loaded

1.4 sec

Page Rendered

304 ms

fawn.com screenshot

About Website

Click here to check amazing Fawn content. Otherwise, check out these important facts you probably never knew about fawn.com

Fawn Industries - Custom Embroidery, Contract Embroidery, Embroidery Digitizing, and Screen Printing, New Park, PA (800) 388-FAWN

Visit fawn.com

Key Findings

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

Performance Metrics

fawn.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

fawn.com

133 ms

fawn.com

224 ms

fawnindustries.css

260 ms

dbushell.css

214 ms

modernizr.js

219 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 79% of them (31 requests) were addressed to the original Fawn.com, 5% (2 requests) were made to Fonts.googleapis.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (622 ms) belongs to the original domain Fawn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 287.4 kB (17%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fawn.com main page is 1.7 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. 40% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 18.5 kB

  • Original 24.9 kB
  • After minification 24.2 kB
  • After compression 6.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 18.5 kB or 74% of the original size.

Image Optimization

-7%

Potential reduce by 93.3 kB

  • Original 1.3 MB
  • After minification 1.2 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. Fawn images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 77.2 kB

  • Original 319.1 kB
  • After minification 317.7 kB
  • After compression 241.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 77.2 kB or 24% of the original size.

CSS Optimization

-91%

Potential reduce by 98.5 kB

  • Original 107.7 kB
  • After minification 91.5 kB
  • After compression 9.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. Fawn.com needs all CSS files to be minified and compressed as it can save up to 98.5 kB or 91% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fawn.com

fawn.com

133 ms

fawn.com

fawn.com

224 ms

fawnindustries.css

fawnindustries.css

260 ms

dbushell.css

dbushell.css

214 ms

modernizr.js

modernizr.js

219 ms

style.css

style.css

218 ms

jquery.js

jquery.js

374 ms

wowslider.js

wowslider.js

219 ms

script.js

script.js

270 ms

api.js

api.js

40 ms

css

css

35 ms

css

css

19 ms

mainBG.jpg

mainBG.jpg

622 ms

Fawn_logo.png

Fawn_logo.png

67 ms

fb.png

fb.png

67 ms

close-btn.png

close-btn.png

67 ms

slide2.jpg

slide2.jpg

261 ms

slide4.jpg

slide4.jpg

209 ms

slide8.jpg

slide8.jpg

200 ms

slide9.jpg

slide9.jpg

264 ms

slide1.jpg

slide1.jpg

212 ms

bullet.png

bullet.png

214 ms

home-img74736.jpg

home-img74736.jpg

262 ms

home-img7495.jpg

home-img7495.jpg

265 ms

UPIC.png

UPIC.png

265 ms

SAGE.png

SAGE.png

313 ms

SAAGNYl.png

SAAGNYl.png

313 ms

PPAI.png

PPAI.png

315 ms

AGI.png

AGI.png

316 ms

ETA.png

ETA.png

316 ms

RA.jpg

RA.jpg

364 ms

contact-img15019.jpg

contact-img15019.jpg

365 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

33 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

35 ms

sdk.js

sdk.js

29 ms

arrows.png

arrows.png

320 ms

pause.png

pause.png

322 ms

recaptcha__en.js

recaptcha__en.js

63 ms

sdk.js

sdk.js

11 ms

Accessibility Review

fawn.com accessibility score

69

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

fawn.com best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fawn.com SEO score

87

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

fawn.com

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