4.6 sec in total
283 ms
3.5 sec
815 ms
Visit whoorl.com now to see the best up-to-date Whoorl content for Canada and also check out these interesting facts you probably never knew about whoorl.com
Clean Beauty and Style Over 40
Visit whoorl.comWe analyzed Whoorl.com page load time and found that the first response time was 283 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
whoorl.com performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value5.4 s
21/100
25%
Value2.0 s
99/100
10%
Value10 ms
100/100
30%
Value0.077
95/100
15%
Value3.5 s
93/100
10%
283 ms
28 ms
136 ms
173 ms
39 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 41% of them (65 requests) were addressed to the original Whoorl.com, 25% (40 requests) were made to Fonts.gstatic.com and 5% (8 requests) were made to S-media-cache-ak0.pinimg.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Socketapi.rafflecopter.com.
Page size can be reduced by 1.9 MB (46%)
4.2 MB
2.3 MB
In fact, the total size of Whoorl.com main page is 4.2 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. 85% 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. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 145.5 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. This page needs HTML code to be minified as it can gain 37.5 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 145.5 kB or 89% of the original size.
Potential reduce by 12.0 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. Whoorl images are well optimized though.
Potential reduce by 959.0 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 959.0 kB or 71% of the original size.
Potential reduce by 813.0 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. Whoorl.com needs all CSS files to be minified and compressed as it can save up to 813.0 kB or 87% of the original size.
Number of requests can be reduced by 71 (65%)
110
39
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whoorl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
whoorl.com
283 ms
css
28 ms
public_widget.css
136 ms
layerslider.css
173 ms
css
39 ms
expanding-archives.css
188 ms
style.css
184 ms
style.css
157 ms
stylesheet.min.css
322 ms
style_dynamic.css
206 ms
font-awesome.min.css
235 ms
style.min.css
251 ms
responsive.min.css
285 ms
style_dynamic_responsive.css
283 ms
js_composer.css
353 ms
custom_css.css
305 ms
style.css
344 ms
style.css
381 ms
jetpack.css
372 ms
css
27 ms
style_2.1.2.css
381 ms
jquery.js
449 ms
jquery-migrate.min.js
390 ms
jquery.carouFredSel-6.1.0-packed.js
424 ms
public_widget.js
421 ms
greensock.js
505 ms
layerslider.kreaturamedia.jquery.js
519 ms
layerslider.transitions.js
481 ms
html5.js
490 ms
script_2.1.2.js
499 ms
external-tracking.min.js
521 ms
launch.js
136 ms
core_widget_ga.js
546 ms
wp-emoji-release.min.js
543 ms
urchin.js
34 ms
expanding-archives.min.js
537 ms
devicepx-jetpack.js
61 ms
gprofiles.js
62 ms
wpgroho.js
534 ms
qode-like.js
543 ms
plugins.js
749 ms
jquery.carouFredSel-6.2.1.js
638 ms
jquery.fullPage.min.js
589 ms
js
112 ms
e-201609.js
6 ms
lemmon-slider.js
600 ms
jquery.mousewheel.min.js
525 ms
jquery.touchSwipe.min.js
514 ms
isotope.pkgd.min.js
550 ms
default_dynamic.js
545 ms
default.min.js
546 ms
custom_js.js
529 ms
comment-reply.min.js
531 ms
js_composer_front.js
539 ms
wp-embed.min.js
528 ms
style.css
430 ms
analytics.js
62 ms
All-Natural-BANNER-300x250-2.jpg
55 ms
wildf4161991375_p1_1-0._UX254_QL90_.jpg
128 ms
c28b520926e89d4ed2a9c9a16a65f181.jpg
440 ms
12383456_195079360856228_2033630670_n.jpg
633 ms
seecl4107712867_p1_1-0._UX254_QL90_.jpg
128 ms
wantl3010087798_p1_1-0._UX254_QL90_.jpg
128 ms
msgma3053314001_p1_1-0._UX254_QL90_.jpg
128 ms
joooa3032012397_p1_1-0._UX254_QL90_.jpg
632 ms
jills4029510652_p1_1-0._UX254_QL90_.jpg
127 ms
whoorl-logo-1.png
461 ms
whoorl-logo-2.png
436 ms
double-pink-lines.png
437 ms
pink-triangle.png
436 ms
jen.jpg
686 ms
invisalign_jl.jpg
446 ms
invisalign_ldc.jpg
714 ms
invisalign_hb.jpg
685 ms
invisalignmab.jpg
578 ms
nc.jpg
632 ms
Whoorl_Profile.png
579 ms
follow-whoorl-on-pinterest-button.png
627 ms
c376e54524ed87bc43ad7536e5b3fa84.jpg
435 ms
8390222bf16bcc90295162ae4ab9c156.jpg
435 ms
a1b15c8a9a31158391142d4e721c0ff5.jpg
436 ms
02339c9fc334ec91a87147879b8330a8.jpg
437 ms
cf4412a46e3d2098a0fc46bdddd828ba.jpg
436 ms
a7f54f808a50ea31621c2d5247403b12.jpg
437 ms
6dc895df25ffd5b86c4e316a923611a7.jpg
438 ms
load.js
397 ms
DzGB83.jpg
486 ms
collect
317 ms
light.png
505 ms
carousel-bg.png
590 ms
vQbQAx9WlNOTTgpOnfyPXQ.woff
311 ms
Li18TEFObx_yGdzKDoI_chsxEYwM7FgeyaSgU71cLG0.woff
313 ms
ZKwULyCG95tk6mOqHQfRBBsxEYwM7FgeyaSgU71cLG0.woff
316 ms
cbAbzEjxTdN5KKmS-gA0tRsxEYwM7FgeyaSgU71cLG0.woff
314 ms
rr0ijB5_2nAJsAoZ6vECXT8E0i7KZn-EPnyo3HZu7kw.woff
317 ms
STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff
317 ms
WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff
318 ms
QoPu455RxV2raYSIFXAMBRsxEYwM7FgeyaSgU71cLG0.woff
316 ms
Ji5epXNcpHu3r63lhS0cThsxEYwM7FgeyaSgU71cLG0.woff
319 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
318 ms
kAYTUNvBOXlHHqglRQ0Nlg.woff
318 ms
1bHRUMxmJHoup12DnI9XmQ.woff
320 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
321 ms
7DI7Kjvwfuz8m3ExKe6m-Q.woff
322 ms
QHIOz1iKF3bIEzRdDFaf5dCpxY7g_VZuMtgz78Sasn8.woff
321 ms
pR0sBQVcY0JZc_ciXjFsK2vhaIAz1NJzluD_h2UBN7c.woff
320 ms
kH7K4InNTm7mmOXXjrA5v2bXv0mI0yfCBzn-qhU0FPM.woff
322 ms
9MkijrV-dEJ0-_NWV7E6Nx-06087kkDBCd_rtr1khsE.woff
322 ms
n7G4PqJvFP2Kubl0VBLDENxHfcsPlDajrhlFKgOPuYg.woff
323 ms
n7G4PqJvFP2Kubl0VBLDEBMHjY5M6rp_NSn2hjKJhfc.woff
323 ms
2NBgzUtEeyB-Xtpr9bm1CShkvU6-zz9BR8nLBmIod8U.woff
322 ms
UC3ZEjagJi85gF9qFaBgIMITpqSvb0EhPNqvdm-qG4s.woff
324 ms
UC3ZEjagJi85gF9qFaBgIIidMZaDCgb76Cj_Fd30HHc.woff
324 ms
G-cgiyv4b0HVLV2M8HoP9A.woff
326 ms
XNVd6tsqi9wmKNvnh5HNED8E0i7KZn-EPnyo3HZu7kw.woff
324 ms
ltAXVgMneoy-oSOU9NjhfPesZW2xOQ-xsNqO47m55DA.woff
326 ms
AcvTq8Q0lyKKNxRlL28Rnz8E0i7KZn-EPnyo3HZu7kw.woff
327 ms
81X-1TO5y4aMK2PPy9kFwz8E0i7KZn-EPnyo3HZu7kw.woff
327 ms
ElegantIcons.woff
658 ms
IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff
324 ms
fontawesome-webfont.woff
612 ms
5xAt7XK2vkUdjhGtt98unSiURDTH4ZeuJyFQH0IObys.woff
327 ms
ZCcPJiCGOzh84o2siPk48dIh4imgI8P11RFo6YPCPC0.woff
327 ms
gtm.js
295 ms
double-blue-lines.png
585 ms
watercolor-splash-1.png
584 ms
7dO2Hj7qB8nRVFK0svQqRj8E0i7KZn-EPnyo3HZu7kw.woff
253 ms
S7vGLZZ40c85SJgiptJGVxa1RVmPjeKy21_GQJaLlJI.woff
253 ms
TVSB8ogXDKMcnAAJ5CqrUha1RVmPjeKy21_GQJaLlJI.woff
254 ms
N2DIbZG4399cPGfifZUEQha1RVmPjeKy21_GQJaLlJI.woff
254 ms
IWp_KHUkJoKURWwpAA2nYNIh4imgI8P11RFo6YPCPC0.woff
253 ms
__utm.gif
194 ms
collect
194 ms
OY22yoG8EJ3IN_muVWm29Ba1RVmPjeKy21_GQJaLlJI.woff
135 ms
lFxvRPuGFG5ktd7P0WRwKha1RVmPjeKy21_GQJaLlJI.woff
134 ms
us4LjTCmlYgh3W8CKujEJha1RVmPjeKy21_GQJaLlJI.woff
131 ms
oY2RadnkHfshu5f0FLsgVRa1RVmPjeKy21_GQJaLlJI.woff
131 ms
DzGB83.jpg
52 ms
main.html
38 ms
main.js
54 ms
load.gif
79 ms
ga.js
65 ms
177 ms
inpage_linkid.js
51 ms
__utm.gif
24 ms
74 ms
1132 ms
1165 ms
1f633.png
307 ms
hovercard.css
77 ms
services.css
128 ms
1f602.png
180 ms
g.gif
20 ms
159 ms
default.css
124 ms
jVG1f1GslU7.png
77 ms
sdk.js
110 ms
whoorl.com 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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
ARIA IDs are not unique
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
Links do not have a discernible name
whoorl.com 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
whoorl.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoorl.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 Whoorl.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.
whoorl.com
Open Graph description is not detected on the main page of Whoorl. 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: