3.6 sec in total
147 ms
2.5 sec
932 ms
Welcome to tonguetieal.com homepage info - get ready to check Tongue Tie AL best content right away, or after learning these important things about tonguetieal.com
We use advanced laser technology to fully release your child’s tongue-tie in a gentle, 15-second procedure.
Visit tonguetieal.comWe analyzed Tonguetieal.com page load time and found that the first response time was 147 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
tonguetieal.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value17.0 s
0/100
25%
Value12.7 s
3/100
10%
Value5,860 ms
0/100
30%
Value0.002
100/100
15%
Value24.4 s
0/100
10%
147 ms
122 ms
102 ms
68 ms
51 ms
Our browser made a total of 168 requests to load all elements on the main page. We found that 57% of them (96 requests) were addressed to the original Tonguetieal.com, 21% (35 requests) were made to Fonts.gstatic.com and 5% (9 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (876 ms) belongs to the original domain Tonguetieal.com.
Page size can be reduced by 470.1 kB (19%)
2.5 MB
2.0 MB
In fact, the total size of Tonguetieal.com main page is 2.5 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 1.4 MB which makes up the majority of the site volume.
Potential reduce by 177.6 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 177.6 kB or 83% of the original size.
Potential reduce by 68.1 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. Tongue Tie AL images are well optimized though.
Potential reduce by 224.4 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 224.4 kB or 28% of the original size.
Potential reduce by 0 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. Tonguetieal.com has all CSS files already compressed.
Number of requests can be reduced by 98 (77%)
127
29
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tongue Tie AL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
tonguetieal.com
147 ms
tonguetieal.com
122 ms
uc-block.bundle.js
102 ms
loader.js
68 ms
upe_blocks.css
51 ms
style.css
67 ms
font-awesome.min.css
79 ms
layout.css
85 ms
css
80 ms
fullcalendar.min.css
107 ms
jquery.qtip.min.css
118 ms
owl.carousel.css
96 ms
woocommerce-layout.css
121 ms
woocommerce.css
125 ms
style.css
132 ms
css
96 ms
style.min.css
304 ms
public.css
131 ms
mediaelementplayer-legacy.min.css
301 ms
wp-mediaelement.min.css
300 ms
pum-site-styles.css
320 ms
formreset.min.css
322 ms
formsmain.min.css
324 ms
readyclass.min.css
328 ms
browsers.min.css
326 ms
magnific_popup.css
330 ms
swiper.css
327 ms
popup.css
331 ms
animate.css
332 ms
readmore.css
326 ms
meta-style.css
327 ms
general.css
329 ms
style-static.min.css
336 ms
style.css
332 ms
jquery.min.js
332 ms
jquery-migrate.min.js
331 ms
masonry.pkgd.min.js
333 ms
imagesloaded.pkgd.min.js
334 ms
jquery.blockUI.min.js
367 ms
add-to-cart.min.js
368 ms
js.cookie.min.js
366 ms
api.js
92 ms
platform.js
104 ms
et-core-unified-tb-6989-6781.min.css
362 ms
et-core-unified-6781.min.css
337 ms
et-core-unified-tb-6989-deferred-6781.min.css
319 ms
wc-blocks.css
308 ms
basic.min.css
301 ms
theme-ie11.min.css
286 ms
bundle_legacy.js
29 ms
theme.min.css
276 ms
woocommerce.min.js
275 ms
jquery.bind-first-0.2.3.min.js
267 ms
js.cookie-2.1.3.min.js
289 ms
public.js
291 ms
jquery.json.min.js
129 ms
gravityforms.min.js
127 ms
css
77 ms
utils.min.js
120 ms
owl.carousel.min.js
120 ms
plugin-script.js
116 ms
idle-timer.min.js
117 ms
custom.js
247 ms
scripts.min.js
247 ms
sourcebuster.min.js
243 ms
order-attribution.min.js
241 ms
mediaelement-and-player.min.js
240 ms
mediaelement-migrate.min.js
253 ms
wp-mediaelement.min.js
250 ms
core.min.js
250 ms
pum-site-scripts.js
249 ms
dom-ready.min.js
250 ms
hooks.min.js
248 ms
i18n.min.js
291 ms
a11y.min.js
257 ms
jquery.maskedinput.min.js
386 ms
placeholders.jquery.min.js
257 ms
vendor-theme.min.js
256 ms
scripts-theme.min.js
254 ms
common.js
382 ms
jquery.magnific-popup.js
381 ms
dsm-magnific-popup-video.js
381 ms
conditional_logic.min.js
381 ms
jquery.fitvids.js
380 ms
fbevents.js
199 ms
fbt.js
659 ms
gtm.js
327 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-logo.svg
656 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-Aboutpage-slider-1.jpg
759 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-The-Facts-Older-Recover-Icon_result.png
658 ms
tongue-tie-icons-sleep_result.png
658 ms
tongue-tie-icons-talk_result.png
657 ms
we-re-so-grateful-After-Tongue-Tie-Release-YouTube.jpg
658 ms
Parent-Testimonial-After-Tongue-Tie-Release-YouTube.jpg
841 ms
Speech-Delayed-Child-With-Tongue-Tie-Gets-29-New-Words-After-Procedure-YouTube.jpg
841 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-homepage-how-work-1.svg
834 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-homepage-how-work-2.svg
836 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-homepage-how-work-3.svg
834 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-book-Tongue-tied.png
852 ms
jra2WxLuB14
294 ms
embed
229 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-footer-logo.svg
876 ms
preloader.gif
723 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-homepage-background.jpg
721 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-dr-richard-baxter-DMD-MS.jpeg
722 ms
Release-Tongue-Ties-Laser-Technology-Tongue-Ties-Birmingham-AL-Dr.-Brigitte-Trego.jpeg
720 ms
release-tongue-ties-laser-technology-tongue-ties-Birmingham-AL-Homepage-CTA.jpg
788 ms
4iCv6KVjbNBYlgoCxCvjvmyL.woff
186 ms
4iCv6KVjbNBYlgoCxCvjvmyI.ttf
187 ms
4iCv6KVjbNBYlgoCjC3jvmyL.woff
518 ms
4iCv6KVjbNBYlgoCjC3jvmyI.ttf
618 ms
4iCs6KVjbNBYlgoKfw7wnU6AFw.woff
518 ms
4iCs6KVjbNBYlgoKcQ7w.woff
518 ms
4iCs6KVjbNBYlgoKcQ7z.ttf
698 ms
4iCv6KVjbNBYlgoC1CzjvmyL.woff
617 ms
4iCv6KVjbNBYlgoC1CzjvmyI.ttf
698 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3iQ.woff
699 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3ig.ttf
702 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTo3iQ.woff
703 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTo3ig.ttf
702 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTo3iQ.woff
703 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTo3ig.ttf
705 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3iQ.woff
706 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3ig.ttf
706 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTo3iQ.woff
706 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTo3ig.ttf
707 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3iQ.woff
707 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3ig.ttf
710 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTo3iQ.woff
708 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTo3ig.ttf
709 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTo3iQ.woff
708 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTo3ig.ttf
707 ms
4iCp6KVjbNBYlgoKejZPslyBN4c.woff
717 ms
4iCp6KVjbNBYlgoKejZPslyBN4Q.ttf
710 ms
4iCp6KVjbNBYlgoKejYHtFyBN4c.woff
783 ms
4iCp6KVjbNBYlgoKejYHtFyBN4Q.ttf
711 ms
4iCu6KVjbNBYlgoKej76l08.woff
711 ms
4iCu6KVjbNBYlgoKej76l0w.ttf
710 ms
4iCp6KVjbNBYlgoKejZftVyBN4c.woff
712 ms
4iCp6KVjbNBYlgoKejZftVyBN4Q.ttf
711 ms
modules.woff
717 ms
languages.json
499 ms
js
573 ms
openbridge3.js
452 ms
2324540254471660
551 ms
www-player.css
316 ms
www-embed-player.js
315 ms
base.js
315 ms
js
409 ms
jra2WxLuB14
224 ms
www-player.css
65 ms
www-embed-player.js
82 ms
base.js
116 ms
woocommerce-smallscreen.css
478 ms
search.js
323 ms
geometry.js
376 ms
main.js
376 ms
261 ms
en.json
190 ms
ad_status.js
271 ms
Uo_dhVY9o5gWds10f-QE3r7w2DYPAY7ZjhqsbDUx1y0.js
75 ms
embed.js
27 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
20 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
21 ms
1px.png
18 ms
127 ms
id
34 ms
translations-en.json
28 ms
tonguetieal.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
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
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.
tonguetieal.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
Browser errors were logged to the console
tonguetieal.com SEO score
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 Tonguetieal.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 Tonguetieal.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.
tonguetieal.com
Open Graph data is detected on the main page of Tongue Tie AL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: