2.6 sec in total
32 ms
1.6 sec
992 ms
Visit about100percent.com now to see the best up-to-date About 100 Percent content for United States and also check out these interesting facts you probably never knew about about100percent.com
Free weblog publishing tool from Google, for sharing text, photos and video.
Visit about100percent.comWe analyzed About100percent.com page load time and found that the first response time was 32 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
about100percent.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value6.9 s
6/100
25%
Value6.0 s
46/100
10%
Value900 ms
31/100
30%
Value0.001
100/100
15%
Value7.8 s
44/100
10%
32 ms
124 ms
38 ms
61 ms
105 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original About100percent.com, 11% (11 requests) were made to Apis.google.com and 8% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (520 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 1.0 MB (54%)
1.9 MB
876.6 kB
In fact, the total size of About100percent.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. 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 217.8 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 217.8 kB or 80% of the original size.
Potential reduce by 136.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, About 100 Percent needs image optimization as it can save up to 136.5 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 661.6 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 661.6 kB or 65% of the original size.
Potential reduce by 6 B
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. About100percent.com has all CSS files already compressed.
Number of requests can be reduced by 44 (48%)
91
47
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of About 100 Percent. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and as a result speed up the page load time.
about100percent.com
32 ms
www.about100percent.com
124 ms
webfont.js
38 ms
3375562265-css_bundle_v2.css
61 ms
authorization.css
105 ms
addthis_widget.js
39 ms
plusone.js
83 ms
show_ads.js
39 ms
stblogger2.js
35 ms
3226477086-widgets.js
41 ms
css
38 ms
cb=gapi.loaded_0
149 ms
cb=gapi.loaded_1
181 ms
google_top_exp.js
146 ms
About%2Bheader%2BJan%2B2016.png
296 ms
icon18_wrench_allbkg.png
179 ms
icon18_edit_allbkg.gif
178 ms
ca-pub-3505411531031386.js
379 ms
zrt_lookup.html
380 ms
show_ads_impl.js
165 ms
IMG_0400.jpg
377 ms
workshop-button-1.png
391 ms
confession%2Bcandy.JPG
371 ms
paging_dot.png
150 ms
jquery-1.4.2.min.js
145 ms
counter_xhtml.js
212 ms
BB-200.png
262 ms
AL_button1.jpg
361 ms
townsquare.jpg
260 ms
ML_published_badge_pink.jpg
260 ms
mfc_protected.png
259 ms
icon18_email.gif
213 ms
skor.jpg
419 ms
SED%2BFB%2BCover%2BFeb%2B2015.png
183 ms
About%2Bfooter%2Bw%2Btext%2B-%2BJan%2B2016.jpg
257 ms
Getting%2Bahead%2B3%2B-%2Bcandy%2B-%2BWMAbout.jpg
419 ms
3004004056_85ed3a17eb_o.jpg
358 ms
About%2Bprofile%2Bpic%2BJan%2B2016.jpg
350 ms
xgzbb53t8j-Mo-vYa23n5onF5uFdDttMLvmWuJdhhgs.ttf
190 ms
C6HYlRF50SGJq1XyXj04z306qf9KHRHwsVx7iw5MXmY.ttf
283 ms
blank.html
96 ms
ads
477 ms
buttons.js
154 ms
navbar.g
152 ms
osd.js
211 ms
t.php
208 ms
ads
448 ms
analytics.js
132 ms
ads
407 ms
ads
520 ms
ads
425 ms
sdk.js
368 ms
300lo.json
117 ms
icons_orange.png
107 ms
platform:gapi.iframes.style.common.js
163 ms
arrows-blue.png
105 ms
sh.8e5f85691f9aaa082472a194.html
64 ms
collect
21 ms
layers.e5ea973510bf60b3db41.js
12 ms
cb=gapi.loaded_0
7 ms
cb=gapi.loaded_1
32 ms
fastbutton
60 ms
postmessageRelay
48 ms
cb=gapi.loaded_0
18 ms
cb=gapi.loaded_1
18 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
36 ms
3193398744-postmessagerelay.js
49 ms
rpc:shindig_random.js
48 ms
s_0RaXcM1FOu_395154613.html
95 ms
s_0RaXcM1FOu_395154613.html
81 ms
m_js_controller.js
88 ms
abg.js
99 ms
cb=gapi.loaded_0
28 ms
adServer.bs
198 ms
creative_add_on.js
197 ms
adServer.bs
201 ms
creative_add_on.js
200 ms
189 ms
s_0RaXcM1FOu_395154613.html
55 ms
favicon
101 ms
googlelogo_color_112x36dp.png
115 ms
nessie_icon_tiamat_white.png
54 ms
s
41 ms
x_button_blue2.png
58 ms
xd_arbiter.php
224 ms
xd_arbiter.php
458 ms
adServer.bs
173 ms
s_0RaXcM1FOu_395154613.html
39 ms
adServer.bs
128 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
10 ms
F4-img-2_1.jpg
50 ms
dvtp_src.js
112 ms
F4-img-2_1.jpg
51 ms
F4-img-2_1.jpg
16 ms
dvtp_src_internal26.js
49 ms
t2tv7.html
157 ms
visit.js
55 ms
about100percent.com accessibility score
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
<frame> or <iframe> elements do not have a title
about100percent.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
General
Impact
Issue
Detected JavaScript libraries
about100percent.com 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
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 About100percent.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 About100percent.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.
about100percent.com
Open Graph description is not detected on the main page of About 100 Percent. 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: