4.2 sec in total
53 ms
2.9 sec
1.3 sec
Click here to check amazing Catchasmile content. Otherwise, check out these important facts you probably never knew about catchasmile.net
Visit catchasmile.netWe analyzed Catchasmile.net page load time and found that the first response time was 53 ms 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.
catchasmile.net performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value10.7 s
0/100
25%
Value11.7 s
4/100
10%
Value1,000 ms
27/100
30%
Value1.281
1/100
15%
Value36.3 s
0/100
10%
53 ms
1424 ms
41 ms
24 ms
46 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 95% of them (127 requests) were addressed to the original Catchasmile.net, 2% (2 requests) were made to Stackpath.bootstrapcdn.com and 2% (2 requests) were made to Cdn.userway.org. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Catchasmile.net.
Page size can be reduced by 742.2 kB (7%)
10.6 MB
9.9 MB
In fact, the total size of Catchasmile.net main page is 10.6 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. Only a small number of websites need less resources to load. Images take 9.5 MB which makes up the majority of the site volume.
Potential reduce by 102.1 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 102.1 kB or 76% of the original size.
Potential reduce by 56.7 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. Catchasmile images are well optimized though.
Potential reduce by 294.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 294.6 kB or 43% of the original size.
Potential reduce by 288.7 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. Catchasmile.net needs all CSS files to be minified and compressed as it can save up to 288.7 kB or 86% of the original size.
Number of requests can be reduced by 36 (29%)
123
87
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Catchasmile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
catchasmile.net
53 ms
www.catchasmile.net
1424 ms
font-awesome.min.css
41 ms
owl.carousel.css
24 ms
owl.theme.css
46 ms
owl.transitions.css
56 ms
jquery.min.js
67 ms
style.min.css
83 ms
styles.css
53 ms
wpr-hamburger.css
80 ms
wprmenu.css
78 ms
wpr-icons.css
79 ms
font-libre-franklin.css
82 ms
style.css
94 ms
blocks.css
87 ms
jquery.fancybox.min.css
92 ms
jquery.min.js
103 ms
jquery-migrate.min.js
102 ms
modernizr.custom.js
102 ms
touchSwipe.js
113 ms
wprmenu.js
114 ms
hooks.min.js
132 ms
i18n.min.js
131 ms
index.js
133 ms
index.js
133 ms
skip-link-focus-fix.js
133 ms
navigation.js
134 ms
global.js
206 ms
jquery.scrollTo.js
216 ms
purify.min.js
216 ms
jquery.fancybox.min.js
217 ms
jquery.easing.min.js
217 ms
api.js
33 ms
wp-polyfill.min.js
220 ms
index.js
219 ms
owl.carousel.js
223 ms
custom.js
218 ms
widget.js
234 ms
repeat-body-image.jpg
101 ms
catchasmile-logo.png
127 ms
address_img_new.png
103 ms
small-arrows-new.png
103 ms
promo-2.jpg
165 ms
promo-5.jpg
104 ms
promo-6.jpg
104 ms
EngagementJPG10-23-e1695931569349.jpg
167 ms
feature-4.png
167 ms
feature-5.png
170 ms
bigplay.png
165 ms
lists-indicator.png
168 ms
refer-friend.png
171 ms
eNewsletter.png
171 ms
wilmington-parent-2020.jpg
173 ms
main-bottom-3.jpg
172 ms
main-bottom-4.jpg
234 ms
aa-1.jpg
174 ms
aa-2.jpg
174 ms
aa-3.jpg
233 ms
aa-4.jpg
234 ms
aa-5.jpg
233 ms
aa-6.jpg
231 ms
aa-8.jpg
232 ms
aa-9.jpg
233 ms
ab-1.jpg
233 ms
libre-franklin-all-400-normal.woff
172 ms
fontawesome-webfont.woff
98 ms
libre-franklin-all-300-normal.woff
152 ms
libre-franklin-all-600-normal.woff
153 ms
libre-franklin-all-800-normal.woff
151 ms
recaptcha__en.js
77 ms
SourceSansPro-Regular-webfont.woff
151 ms
SourceSansPro-Light-webfont.woff
150 ms
SourceSansPro-ExtraLight-webfont.woff
151 ms
ab-2.jpg
147 ms
ab-3.jpg
145 ms
ac1-wilmington-pediatric-dentistry-superheros.jpg
146 ms
ac2-doctors.jpg
147 ms
ac3-beth_and_dawn.jpg
172 ms
ac4-Jersey_Day.jpg
145 ms
ac4-superhero.jpg
172 ms
ac5-Megan.jpg
171 ms
widget_app_base_1731678445949.js
46 ms
ac6-paint.jpg
151 ms
ac7-pedi.jpg
111 ms
ac9-color.jpg
111 ms
b1-doc2.jpg
111 ms
b2-CFA-2.jpg
114 ms
b4-CHICKFILA2.jpg
113 ms
b5-Cow_Day-2.jpg
113 ms
b6-TOTUS.jpg
114 ms
b7-olafspalsh.jpg
112 ms
b8-soccer.jpg
116 ms
b9-Soccer2.jpg
124 ms
c1-walk.jpg
128 ms
c2-Santa_Splash.jpg
71 ms
c3-Dr_Steph.jpg
71 ms
c3-all-staff.jpg
86 ms
c4-CB_Parade.jpg
77 ms
c5-Tacky_Sweaters.jpg
85 ms
c6.jpg
94 ms
c7.jpg
92 ms
c8.jpg
96 ms
c9.jpg
101 ms
d1.jpg
102 ms
d2.jpg
109 ms
d3.jpg
117 ms
d4.jpg
112 ms
d5.jpg
118 ms
d6.jpg
120 ms
d7.jpg
123 ms
d8.jpg
129 ms
d9.jpg
131 ms
e1.jpg
137 ms
e2.jpg
131 ms
e3.jpg
111 ms
e4.jpg
115 ms
e5.jpg
119 ms
e6.jpg
128 ms
e7.jpg
122 ms
facebook.png
130 ms
twitter.png
128 ms
instagram.png
131 ms
google-plus.png
136 ms
you-tube.png
142 ms
pinterest.png
143 ms
bottom-image.jpg
142 ms
wilmington-pediatric-dental-logo-150x150-1.png
145 ms
aapd-75x75-1.png
143 ms
ada-75x75-1.png
137 ms
abpd-diplomate-75x75-1.png
142 ms
large-arrows1.png
149 ms
large-arrows.png
25 ms
small-arrows.png
20 ms
catchasmile.net 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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
catchasmile.net 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
catchasmile.net 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 Catchasmile.net 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 Catchasmile.net 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.
catchasmile.net
Open Graph description is not detected on the main page of Catchasmile. 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: