Tools & Wizards About Us
frepple.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

frepple.com

Home - frepple

Page Load Speed

4.2 sec in total

First Response

337 ms

Resources Loaded

3.6 sec

Page Rendered

200 ms

frepple.com screenshot

About Website

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

Frepple is an easy-to-implement upgrade for your spreadsheet-based planning processes.

Visit frepple.com

Key Findings

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

Performance Metrics

frepple.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value1,550 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.559

13/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

frepple.com

337 ms

frepple.com

1846 ms

open_sans.css

92 ms

page-list.css

175 ms

flexslider.css

274 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 97% of them (60 requests) were addressed to the original Frepple.com, 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Frepple.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 313.7 kB (37%)

Content Size

850.6 kB

After Optimization

537.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 26.2 kB

  • Original 33.2 kB
  • After minification 31.6 kB
  • After compression 7.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. 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 26.2 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 5.1 kB

  • Original 418.1 kB
  • After minification 413.1 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. Frepple images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 191.5 kB

  • Original 289.3 kB
  • After minification 259.4 kB
  • After compression 97.8 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 191.5 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 90.9 kB

  • Original 110.0 kB
  • After minification 87.4 kB
  • After compression 19.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. Frepple.com needs all CSS files to be minified and compressed as it can save up to 90.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (77%)

Requests Now

56

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frepple.com

frepple.com

337 ms

frepple.com

frepple.com

1846 ms

open_sans.css

open_sans.css

92 ms

page-list.css

page-list.css

175 ms

flexslider.css

flexslider.css

274 ms

reset.css

reset.css

265 ms

screen.css

screen.css

268 ms

element.css

element.css

265 ms

media-queries.css

media-queries.css

258 ms

style.css

style.css

261 ms

uamAdmin.css

uamAdmin.css

365 ms

uamLoginForm.css

uamLoginForm.css

366 ms

modernizr.custom.js

modernizr.custom.js

352 ms

respond.min.js

respond.min.js

349 ms

jquery.js

jquery.js

481 ms

jquery-migrate.min.js

jquery-migrate.min.js

390 ms

functions.js

functions.js

462 ms

comment-reply.min.js

comment-reply.min.js

435 ms

jquery.form.min.js

jquery.form.min.js

448 ms

jquery.metadata.js

jquery.metadata.js

449 ms

jquery.validate.min.js

jquery.validate.min.js

474 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

529 ms

supersubs.js

supersubs.js

572 ms

jquery.imagesloaded.js

jquery.imagesloaded.js

575 ms

jquery.retina-0.1.js

jquery.retina-0.1.js

576 ms

html5.js

html5.js

576 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

578 ms

bootstrap-twipsy.js

bootstrap-twipsy.js

611 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

618 ms

jquery.fitvids.js

jquery.fitvids.js

627 ms

jquery.bgpos.js

jquery.bgpos.js

631 ms

jquery.quicksand.js

jquery.quicksand.js

641 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

681 ms

grizzly-core.js

grizzly-core.js

682 ms

anti-spam-4.2.js

anti-spam-4.2.js

706 ms

wp-embed.min.js

wp-embed.min.js

706 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

655 ms

frepple.svg

frepple.svg

352 ms

footer-shadow.png

footer-shadow.png

354 ms

slide_machine1.png

slide_machine1.png

512 ms

slide_manometer.png

slide_manometer.png

446 ms

slide_pallets.png

slide_pallets.png

530 ms

slide_machine21.png

slide_machine21.png

556 ms

302.png

302.png

365 ms

66.png

66.png

378 ms

136.png

136.png

472 ms

304.png

304.png

460 ms

300.png

300.png

529 ms

135.png

135.png

545 ms

linkedin_logo.png

linkedin_logo.png

585 ms

chess.png

chess.png

606 ms

subscribe-bt.png

subscribe-bt.png

596 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

606 ms

OpenSans-Light.woff

OpenSans-Light.woff

622 ms

OpenSans-Semibold.woff

OpenSans-Semibold.woff

621 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

722 ms

ga.js

ga.js

29 ms

__utm.gif

__utm.gif

22 ms

chess-bar.png

chess-bar.png

104 ms

app-prev-light.png

app-prev-light.png

85 ms

app-next-light.png

app-next-light.png

86 ms

black-50.png

black-50.png

85 ms

Accessibility Review

frepple.com accessibility score

79

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-*] attributes do not match their roles

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

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

frepple.com best practices score

83

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

SEO Factors

frepple.com SEO score

92

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

Links do not have descriptive text

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

frepple.com

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