Tools & Wizards About Us
foobl.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

foobl.com

Vancouver, WA Magento and PHP Web Development | Foobl, LLC

Page Load Speed

6.5 sec in total

First Response

79 ms

Resources Loaded

6.2 sec

Page Rendered

155 ms

foobl.com screenshot

About Website

Welcome to foobl.com homepage info - get ready to check Foobl best content right away, or after learning these important things about foobl.com

Foobl is a development agency based in Sacramento, CA with experience working on PHP websites. We have worked on WordPress, Magento, Laravel and custom websites for clients both big and small.

Visit foobl.com

Key Findings

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

Performance Metrics

foobl.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.7 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

foobl.com

79 ms

foobl.com

276 ms

www.foobl.com

1476 ms

style.min.css

242 ms

styles.css

368 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 90% of them (98 requests) were addressed to the original Foobl.com, 5% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Foobl.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 266.9 kB (14%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foobl.com main page is 1.9 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. 50% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 68.4 kB

  • Original 85.3 kB
  • After minification 80.9 kB
  • After compression 16.9 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 68.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 898 B

  • Original 294.3 kB
  • After minification 293.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. Foobl images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 170.6 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 1.2 MB

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

CSS Optimization

-24%

Potential reduce by 27.0 kB

  • Original 110.4 kB
  • After minification 110.4 kB
  • After compression 83.4 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. Foobl.com needs all CSS files to be minified and compressed as it can save up to 27.0 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 94 (94%)

Requests Now

100

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foobl.com

foobl.com

79 ms

foobl.com

foobl.com

276 ms

www.foobl.com

www.foobl.com

1476 ms

style.min.css

style.min.css

242 ms

styles.css

styles.css

368 ms

style.css

style.css

324 ms

css

css

44 ms

material-design-iconic-font.min.css

material-design-iconic-font.min.css

260 ms

bootstrap.min.css

bootstrap.min.css

321 ms

material.min.css

material.min.css

291 ms

animate.min.css

animate.min.css

506 ms

owl.carousel.css

owl.carousel.css

538 ms

owl.theme.css

owl.theme.css

557 ms

owl.transitions.css

owl.transitions.css

562 ms

magnific-popup.css

magnific-popup.css

623 ms

sweet-alert.min.css

sweet-alert.min.css

655 ms

ie9.css

ie9.css

749 ms

common.css

common.css

814 ms

style.css

style.css

804 ms

responsive.css

responsive.css

835 ms

addthis_wordpress_public.min.css

addthis_wordpress_public.min.css

893 ms

enlighterjs.min.css

enlighterjs.min.css

911 ms

smartslider.min.css

smartslider.min.css

998 ms

css

css

43 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1040 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1057 ms

wp-polyfill.min.js

wp-polyfill.min.js

1074 ms

autop.min.js

autop.min.js

1150 ms

blob.min.js

blob.min.js

1172 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

1277 ms

react.min.js

react.min.js

1291 ms

hooks.min.js

hooks.min.js

1301 ms

deprecated.min.js

deprecated.min.js

1310 ms

dom.min.js

dom.min.js

1390 ms

react-dom.min.js

react-dom.min.js

1434 ms

escape-html.min.js

escape-html.min.js

1531 ms

element.min.js

element.min.js

1528 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

1537 ms

i18n.min.js

i18n.min.js

1547 ms

keycodes.min.js

keycodes.min.js

1494 ms

addthis_widget.js

addthis_widget.js

27 ms

api.js

api.js

44 ms

priority-queue.min.js

priority-queue.min.js

1674 ms

compose.min.js

compose.min.js

1512 ms

private-apis.min.js

private-apis.min.js

1554 ms

redux-routine.min.js

redux-routine.min.js

1507 ms

data.min.js

data.min.js

1459 ms

html-entities.min.js

html-entities.min.js

1505 ms

shortcode.min.js

shortcode.min.js

1580 ms

blocks.min.js

blocks.min.js

1516 ms

dom-ready.min.js

dom-ready.min.js

1501 ms

a11y.min.js

a11y.min.js

1527 ms

moment.min.js

moment.min.js

1520 ms

date.min.js

date.min.js

1468 ms

primitives.min.js

primitives.min.js

1550 ms

rich-text.min.js

rich-text.min.js

1563 ms

warning.min.js

warning.min.js

1480 ms

components.min.js

components.min.js

1553 ms

url.min.js

url.min.js

1499 ms

api-fetch.min.js

api-fetch.min.js

1472 ms

lodash.min.js

lodash.min.js

1540 ms

keyboard-shortcuts.min.js

keyboard-shortcuts.min.js

1549 ms

notices.min.js

notices.min.js

1546 ms

preferences-persistence.min.js

preferences-persistence.min.js

1527 ms

preferences.min.js

preferences.min.js

1545 ms

style-engine.min.js

style-engine.min.js

1476 ms

token-list.min.js

token-list.min.js

1539 ms

wordcount.min.js

wordcount.min.js

1555 ms

block-editor.min.js

block-editor.min.js

1559 ms

core-data.min.js

core-data.min.js

1392 ms

media-utils.min.js

media-utils.min.js

1559 ms

reusable-blocks.min.js

reusable-blocks.min.js

1493 ms

server-side-render.min.js

server-side-render.min.js

1501 ms

editor.min.js

editor.min.js

1473 ms

block.build.js

block.build.js

1402 ms

jquery.min.js

jquery.min.js

1600 ms

jquery-migrate.min.js

jquery-migrate.min.js

1623 ms

n2.min.js

n2.min.js

1578 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

1506 ms

ss-simple.min.js

ss-simple.min.js

1493 ms

smartslider-backgroundanimation.min.js

smartslider-backgroundanimation.min.js

1470 ms

email-decode.min.js

email-decode.min.js

1344 ms

index.js

index.js

1558 ms

index.js

index.js

1591 ms

material.min.js

material.min.js

1488 ms

all-plugins.js

all-plugins.js

1409 ms

common-plugins.js

common-plugins.js

1391 ms

owl.carousel.min.js

owl.carousel.min.js

1401 ms

sweet-alert.min.js

sweet-alert.min.js

1379 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1602 ms

jwplayer.js

jwplayer.js

1460 ms

common.js

common.js

1405 ms

all-components.js

all-components.js

1377 ms

main.js

main.js

1387 ms

index.js

index.js

1354 ms

enlighterjs.min.js

enlighterjs.min.js

1548 ms

logo_orange_sm.png

logo_orange_sm.png

767 ms

logo_white_sm.png

logo_white_sm.png

765 ms

rev_img_1.jpg

rev_img_1.jpg

782 ms

gtm.js

gtm.js

80 ms

twiiter_bg.jpg

twiiter_bg.jpg

806 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

17 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

23 ms

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

37 ms

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

42 ms

KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf

52 ms

Material-Design-Iconic-Font.woff

Material-Design-Iconic-Font.woff

883 ms

recaptcha__en.js

recaptcha__en.js

25 ms

print.css

print.css

266 ms

Accessibility Review

foobl.com accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

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

Best Practices

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

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

Missing source maps for large first-party JavaScript

SEO Factors

foobl.com SEO score

100

Search Engine Optimization Advices

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

    UTF-8

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

foobl.com

Open Graph data is detected on the main page of Foobl. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: