Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

febcorp.com

Foodservice Equipment Brokers

Page Load Speed

5 sec in total

First Response

1.1 sec

Resources Loaded

3.4 sec

Page Rendered

490 ms

febcorp.com screenshot

About Website

Visit febcorp.com now to see the best up-to-date Febcorp content and also check out these interesting facts you probably never knew about febcorp.com

Serving those who serve others! Shop a wide variety of commercial restaurant equipment and supplies.

Visit febcorp.com

Key Findings

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

Performance Metrics

febcorp.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value39.4 s

0/100

25%

SI (Speed Index)

Value34.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value62.7 s

0/100

10%

Network Requests Diagram

febcorp.com

1149 ms

d84dec9172e5e34b182430a31083bad8.min.css

164 ms

styles-l.min.css

146 ms

959f38392f4d8d16b0778f672413c53b.min.js

98 ms

js

71 ms

Our browser made a total of 246 requests to load all elements on the main page. We found that 89% of them (218 requests) were addressed to the original Febcorp.com, 5% (13 requests) were made to Embed.tawk.to and 3% (8 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Febcorp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 832.4 kB (7%)

Content Size

12.1 MB

After Optimization

11.3 MB

In fact, the total size of Febcorp.com main page is 12.1 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. 85% 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 11.6 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 222.1 kB

  • Original 246.1 kB
  • After minification 210.5 kB
  • After compression 24.0 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 35.6 kB, which is 14% 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 222.1 kB or 90% of the original size.

Image Optimization

-5%

Potential reduce by 604.3 kB

  • Original 11.6 MB
  • After minification 11.0 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. Febcorp images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 5.5 kB

  • Original 142.4 kB
  • After minification 142.3 kB
  • After compression 136.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 515 B

  • Original 136.6 kB
  • After minification 136.6 kB
  • After compression 136.0 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. Febcorp.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 144 (60%)

Requests Now

242

After Optimization

98

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

Accessibility Review

febcorp.com accessibility score

68

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

febcorp.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

febcorp.com SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Febcorp.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 Febcorp.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

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