Tools & Wizards About Us
benefitsstore.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

benefitsstore.com

California Individual and Group Free Health Insurance Quote

Page Load Speed

6.3 sec in total

First Response

2.1 sec

Resources Loaded

4.1 sec

Page Rendered

59 ms

benefitsstore.com screenshot

About Website

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

Los Angeles and Temecula Health Insurance Quote. Get your FREE health insurance quote from an expert insurance advisor. Helping Californians since 1984!

Visit benefitsstore.com

Key Findings

We analyzed Benefitsstore.com page load time and found that the first response time was 2.1 sec and then it took 4.2 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

benefitsstore.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

www.benefitsstore.com

2084 ms

minified.js

47 ms

focus-within-polyfill.js

46 ms

polyfill.min.js

1133 ms

thunderbolt-commons.14431d95.bundle.min.js

69 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Benefitsstore.com, 33% (20 requests) were made to Static.parastorage.com and 32% (19 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Benefitsstore.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 672.2 kB (60%)

Content Size

1.1 MB

After Optimization

453.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Benefitsstore.com main page is 1.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. 50% of websites need less resources to load. HTML takes 702.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 565.4 kB

  • Original 702.4 kB
  • After minification 700.6 kB
  • After compression 136.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 565.4 kB or 81% of the original size.

Image Optimization

-27%

Potential reduce by 26.3 kB

  • Original 95.7 kB
  • After minification 69.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, Benefitsstore needs image optimization as it can save up to 26.3 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 80.5 kB

  • Original 327.8 kB
  • After minification 327.8 kB
  • After compression 247.3 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 80.5 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (35%)

Requests Now

40

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.benefitsstore.com

www.benefitsstore.com

2084 ms

minified.js

minified.js

47 ms

focus-within-polyfill.js

focus-within-polyfill.js

46 ms

polyfill.min.js

polyfill.min.js

1133 ms

thunderbolt-commons.14431d95.bundle.min.js

thunderbolt-commons.14431d95.bundle.min.js

69 ms

main.e99c0319.bundle.min.js

main.e99c0319.bundle.min.js

67 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

67 ms

lodash.min.js

lodash.min.js

70 ms

react.production.min.js

react.production.min.js

71 ms

react-dom.production.min.js

react-dom.production.min.js

73 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

69 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

70 ms

brevo-conversations.js

brevo-conversations.js

165 ms

Heartlogo110.png

Heartlogo110.png

91 ms

25aa17_9de9b2c6754b42c68fa8a570f4f11389~mv2.jpg

25aa17_9de9b2c6754b42c68fa8a570f4f11389~mv2.jpg

246 ms

shutterstock_2282908411_edited.jpg

shutterstock_2282908411_edited.jpg

369 ms

shutterstock_2312975421_edited.jpg

shutterstock_2312975421_edited.jpg

335 ms

shutterstock_570119506_edited.jpg

shutterstock_570119506_edited.jpg

394 ms

shutterstock_398306131_edited.jpg

shutterstock_398306131_edited.jpg

436 ms

25aa17_9a820601be8e4599ac9e644b7213e754~mv2.jpg

25aa17_9a820601be8e4599ac9e644b7213e754~mv2.jpg

355 ms

25aa17_344a693acbc44e9987217444fb0aa48f~mv2.png

25aa17_344a693acbc44e9987217444fb0aa48f~mv2.png

435 ms

25aa17_ec5d3b29ccbf4644b5df6f84b24845ff~mv2.jpg

25aa17_ec5d3b29ccbf4644b5df6f84b24845ff~mv2.jpg

555 ms

25aa17_a72560ffa6e54de4b1234b1bd32707f3~mv2.png

25aa17_a72560ffa6e54de4b1234b1bd32707f3~mv2.png

757 ms

25aa17_a5a40e60bea74302851afb5dee46de70~mv2.png

25aa17_a5a40e60bea74302851afb5dee46de70~mv2.png

631 ms

25aa17_bf1900a9082d404eaa0ccd0ab563b750~mv2.png

25aa17_bf1900a9082d404eaa0ccd0ab563b750~mv2.png

589 ms

Colonial%20Logo%205.png

Colonial%20Logo%205.png

590 ms

morgan%20white_edited.png

morgan%20white_edited.png

612 ms

25aa17_ca153557d7d1477bad694d6815f1240f~mv2.png

25aa17_ca153557d7d1477bad694d6815f1240f~mv2.png

757 ms

25aa17_f3d855c1842a4080af782b656b114fd6~mv2.png

25aa17_f3d855c1842a4080af782b656b114fd6~mv2.png

765 ms

25aa17_2fd5bd5b32f54078a653c642439ea417~mv2.jpg

25aa17_2fd5bd5b32f54078a653c642439ea417~mv2.jpg

781 ms

25aa17_eccbe2aeaf03421b9b48ab8899b26095~mv2.png

25aa17_eccbe2aeaf03421b9b48ab8899b26095~mv2.png

816 ms

25aa17_649d06b50786477fb1240369bd25349c~mv2.png

25aa17_649d06b50786477fb1240369bd25349c~mv2.png

813 ms

bundle.min.js

bundle.min.js

106 ms

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

22 ms

AvenirLTW05-85Heavy.woff

AvenirLTW05-85Heavy.woff

21 ms

c5749443-93da-4592-b794-42f28d62ef72.woff

c5749443-93da-4592-b794-42f28d62ef72.woff

21 ms

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

21 ms

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

21 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

21 ms

AvenirLTW05-35Light.woff

AvenirLTW05-35Light.woff

41 ms

conversations-widget.brevo.com

conversations-widget.brevo.com

70 ms

112 ms

104 ms

105 ms

105 ms

101 ms

99 ms

144 ms

144 ms

143 ms

139 ms

138 ms

138 ms

599bedf87eed214815c63351aca105cd7084553c.css

599bedf87eed214815c63351aca105cd7084553c.css

44 ms

meteor_runtime_config.js

meteor_runtime_config.js

36 ms

89e174445804bfce74c25b0e9604677dac76d205.js

89e174445804bfce74c25b0e9604677dac76d205.js

53 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

22 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

6 ms

Accessibility Review

benefitsstore.com accessibility score

99

Accessibility Issues

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

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

Missing source maps for large first-party JavaScript

SEO Factors

benefitsstore.com SEO score

90

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

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

benefitsstore.com

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