Tools & Wizards About Us
figlife.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

figlife.com

Fig Life - Fig Trees and Cuttings, Fig Varieties

Page Load Speed

889 ms in total

First Response

187 ms

Resources Loaded

553 ms

Page Rendered

149 ms

figlife.com screenshot

About Website

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

FigLife sells a huge selection of fig cuttings and fig trees nationwide! Visit FigLife.com to learn about rare fig varieties and successful growing techniques!

Visit figlife.com

Key Findings

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

Performance Metrics

figlife.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

figlife.com

187 ms

background.gif

114 ms

clear.gif

112 ms

header.jpg

296 ms

main.jpg

367 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 20% of them (1 request) were addressed to the original Figlife.com, 80% (4 requests) were made to Images.secureserver.net. The less responsive or slowest element that took the longest time to load (367 ms) relates to the external source Images.secureserver.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.9 kB (16%)

Content Size

48.2 kB

After Optimization

40.3 kB

  • HTML
  • Images

In fact, the total size of Figlife.com main page is 48.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 45.3 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 2.0 kB

  • Original 2.9 kB
  • After minification 2.7 kB
  • After compression 821 B

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 2.0 kB or 71% of the original size.

Image Optimization

-13%

Potential reduce by 5.8 kB

  • Original 45.3 kB
  • After minification 39.5 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. Obviously, Fig Life needs image optimization as it can save up to 5.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • Images

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fig Life. According to our analytics all requests are already optimized.

Network Requests Diagram

figlife.com

figlife.com

187 ms

background.gif

background.gif

114 ms

clear.gif

clear.gif

112 ms

header.jpg

header.jpg

296 ms

main.jpg

main.jpg

367 ms

Accessibility Review

figlife.com accessibility score

81

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

button, link, and menuitem elements do not have accessible names.

High

[role]s are not contained by their required parent element

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

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

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

Best Practices

figlife.com best practices score

92

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

Page has valid source maps

SEO Factors

figlife.com SEO score

78

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Figlife.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 Figlife.com main page’s claimed encoding is iso-8859-1. 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

figlife.com

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