Report Summary

  • 0

    Performance

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

frango.com

Frango Chocolate Gift Boxes | Garrett Popcorn Shops

Page Load Speed

3.7 sec in total

First Response

1.1 sec

Resources Loaded

2.4 sec

Page Rendered

142 ms

frango.com screenshot

About Website

Visit frango.com now to see the best up-to-date Frango content for United States and also check out these interesting facts you probably never knew about frango.com

Make a small moment special with our new beautiful Frango Chocolate gift boxes. Shop now!

Visit frango.com

Key Findings

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

Performance Metrics

frango.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value29.3 s

0/100

25%

SI (Speed Index)

Value22.6 s

0/100

10%

TBT (Total Blocking Time)

Value4,300 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value1.415

0/100

15%

TTI (Time to Interactive)

Value31.7 s

0/100

10%

Network Requests Diagram

frango.com

1088 ms

610 ms

cs-start

121 ms

theme-bundle.head_async.js

125 ms

css

120 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Frango.com, 28% (23 requests) were made to Cdn11.bigcommerce.com and 10% (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 Frango.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.3 kB (13%)

Content Size

1.0 MB

After Optimization

887.0 kB

In fact, the total size of Frango.com main page is 1.0 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 528.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 123.9 kB

  • Original 153.2 kB
  • After minification 141.8 kB
  • After compression 29.3 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 123.9 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 528.4 kB
  • After minification 528.4 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. Frango images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 12.3 kB

  • Original 332.4 kB
  • After minification 332.4 kB
  • After compression 320.2 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

-2%

Potential reduce by 219 B

  • Original 9.4 kB
  • After minification 9.4 kB
  • After compression 9.1 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. Frango.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 55 (73%)

Requests Now

75

After Optimization

20

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

Accessibility Review

frango.com accessibility score

83

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

frango.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

frango.com SEO score

86

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frango.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 Frango.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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