1.9 sec in total
155 ms
1.6 sec
132 ms
Welcome to simple.us homepage info - get ready to check Simple best content for United States right away, or after learning these important things about simple.us
Simple Dental and Life Plans provide an upgrade to traditional dental and life plans created last century.
Visit simple.usWe analyzed Simple.us page load time and found that the first response time was 155 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
simple.us performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value6.9 s
6/100
25%
Value4.0 s
81/100
10%
Value1,040 ms
25/100
30%
Value0
100/100
15%
Value8.8 s
35/100
10%
155 ms
39 ms
138 ms
63 ms
65 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Simple.us, 69% (43 requests) were made to Static.parastorage.com and 13% (8 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (553 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.6 MB (77%)
3.4 MB
759.4 kB
In fact, the total size of Simple.us main page is 3.4 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. Javascripts take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 298 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 298 B or 44% of the original size.
Potential reduce by 541 B
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, Simple needs image optimization as it can save up to 541 B or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.4 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 2.4 MB or 77% of the original size.
Potential reduce by 176.6 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. Simple.us needs all CSS files to be minified and compressed as it can save up to 176.6 kB or 85% of the original size.
Number of requests can be reduced by 47 (84%)
56
9
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Simple. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
simple.us
155 ms
simplelife
39 ms
bt
138 ms
require.min.js
63 ms
main-r.min.js
65 ms
viewer.css
92 ms
UpgradeBrowser.js
94 ms
dynamicmodel
56 ms
496625_2d4d257ae9f7d679d6303d342e7494cf_102.json.z
549 ms
496625_2478224e5e3942404522c8939a27e028_99.json.z
553 ms
ugc-viewer
68 ms
bt
142 ms
skins.min.js
126 ms
components.min.js
121 ms
utils.min.js
120 ms
core.min.js
66 ms
react-with-addons.min.js
118 ms
lodash.min.js
113 ms
TweenMax.min.js
120 ms
layout.min.js
118 ms
tpa.min.js
115 ms
fonts.min.js
113 ms
animations.min.js
103 ms
swfobject.min.js
101 ms
mousetrap.min.js
107 ms
tweenEngine.min.js
106 ms
DrawSVGPlugin.min.js
106 ms
react-dom.min.js
108 ms
ScrollToPlugin.min.js
110 ms
widgets.min.js
108 ms
experiment.js
108 ms
render.min.js
108 ms
wixappsCore.min.js
112 ms
wixappsClassics.min.js
113 ms
wixappsBuilder.min.js
109 ms
zepto.min.js
106 ms
color.min.js
108 ms
react-dom-server.min.js
323 ms
bt
105 ms
latin.css
41 ms
dc.js
284 ms
bt
267 ms
1f3c0f_b779c033eee84ab98788409e0494a7a1.png
234 ms
mobileIEFix.css
62 ms
css
69 ms
Collage.html
66 ms
bt
174 ms
bt
174 ms
jquery.min.js
140 ms
jquery.easing-1.3.min.js
138 ms
lodash.min.js
137 ms
webfont.js
267 ms
Wix.js
263 ms
style.min.css
156 ms
app.min.js
155 ms
bt
133 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
7 ms
opensans-regular-webfont.woff
9 ms
opensans-bold-webfont.woff
98 ms
opensans-italic-webfont.woff
97 ms
opensans-bolditalic-webfont.woff
97 ms
ga-audiences
128 ms
simple.us accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
simple.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
simple.us SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Simple.us 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 Simple.us 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.
simple.us
Open Graph description is not detected on the main page of Simple. 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: