7.6 sec in total
610 ms
3.9 sec
3.1 sec
Visit aivee.ph now to see the best up-to-date Aivee content for Philippines and also check out these interesting facts you probably never knew about aivee.ph
ABOUT US The Aivee brand is named after their president and medical director, Dr. Aivee Teo, who established the clinic alongside her husband, Dr. Z’Shen Teo. Throughout the years, the field of Cosmet...
Visit aivee.phWe analyzed Aivee.ph page load time and found that the first response time was 610 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
aivee.ph performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value16.3 s
0/100
25%
Value14.0 s
1/100
10%
Value670 ms
44/100
30%
Value0.001
100/100
15%
Value24.9 s
0/100
10%
610 ms
459 ms
137 ms
237 ms
189 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Aivee.ph, 76% (104 requests) were made to Theaiveeclinic.com and 18% (25 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Theaiveeclinic.com.
Page size can be reduced by 223.3 kB (4%)
5.3 MB
5.1 MB
In fact, the total size of Aivee.ph main page is 5.3 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 4.7 MB which makes up the majority of the site volume.
Potential reduce by 159.9 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 159.9 kB or 84% of the original size.
Potential reduce by 40.3 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. Aivee images are well optimized though.
Potential reduce by 17.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. This website has mostly compressed JavaScripts.
Potential reduce by 5.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. Aivee.ph has all CSS files already compressed.
Number of requests can be reduced by 80 (73%)
109
29
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aivee. 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 22 to 1 for CSS and as a result speed up the page load time.
aivee.ph
610 ms
theaiveeclinic.com
459 ms
fcjes.css
137 ms
fcjes.css
237 ms
fcjes.css
189 ms
fcjes.css
193 ms
fcjes.css
331 ms
post-13923.css
207 ms
fcjes.css
209 ms
post-13.css
249 ms
post-63.css
252 ms
post-74.css
261 ms
post-141.css
270 ms
fcjes.css
298 ms
post-273.css
303 ms
post-329.css
299 ms
post-386.css
323 ms
post-521.css
326 ms
css
60 ms
fcjes.js
421 ms
fcjes.js
413 ms
fcjes.js
413 ms
fcjes.js
469 ms
fcjes.js
414 ms
fcjes.js
415 ms
fcjes.js
416 ms
fcjes.js
416 ms
fcjes.css
467 ms
js
84 ms
fcjes.css
467 ms
fcjes.css
463 ms
fcjgg.css
463 ms
script.js
465 ms
frontend.min.js
520 ms
dynamic-conditions-public.js
522 ms
jquery.blockUI.min.js
521 ms
add-to-cart.min.js
522 ms
js.cookie.min.js
524 ms
woocommerce.min.js
523 ms
cart-fragments.min.js
878 ms
site_main.js
588 ms
awdr-dynamic-price.js
731 ms
slick.min.js
736 ms
accordion.min.js
720 ms
hello-frontend.min.js
715 ms
smush-lazy-load.min.js
692 ms
general.min.js
767 ms
tooltipster.bundle.min.js
766 ms
front.js
757 ms
radio.js
748 ms
checkbox.js
723 ms
select.js
716 ms
mselect.js
966 ms
chosen.jquery.js
951 ms
slider.min.js
860 ms
jquery-ui-touch-punch.min.js
860 ms
accounting.min.js
859 ms
price-slider.min.js
859 ms
jquery.smartmenus.min.js
970 ms
imagesloaded.min.js
967 ms
webpack-pro.runtime.min.js
969 ms
webpack.runtime.min.js
917 ms
frontend-modules.min.js
919 ms
regenerator-runtime.min.js
889 ms
wp-polyfill.min.js
1084 ms
hooks.min.js
1081 ms
i18n.min.js
1079 ms
frontend.min.js
1079 ms
xfbml.customerchat.js
386 ms
waypoints.min.js
1044 ms
frontend.min.js
1025 ms
elements-handlers.min.js
1211 ms
jquery.sticky.min.js
1184 ms
jquery.zoom.min.js
1207 ms
jquery.flexslider.min.js
1183 ms
analytics.js
428 ms
photoswipe.min.js
1008 ms
photoswipe-ui-default.min.js
853 ms
underscore.min.js
857 ms
wp-util.min.js
854 ms
add-to-cart-variation.min.js
856 ms
single-product.min.js
856 ms
9947.js
856 ms
top-head@2x_compressed.jpg
847 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
392 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
524 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
524 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
525 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
610 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
654 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
658 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
656 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
644 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
644 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
645 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
646 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
652 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
647 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
646 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B1i03Sup5.ttf
737 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B7y03Sup5.ttf
649 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BAyo3Sup5.ttf
648 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSo3Sup5.ttf
752 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf
752 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf
757 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf
756 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf
773 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf
776 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf
774 ms
star.woff
841 ms
1_compressed.jpg
1024 ms
3_compressed.jpg
1024 ms
4_compressed.jpg
1024 ms
5_compressed.jpg
1021 ms
6_compressed.jpg
1097 ms
676 ms
collect
169 ms
7_compressed.jpg
786 ms
8_compressed.jpg
903 ms
9_compressed.jpg
786 ms
10_compressed.jpg
786 ms
11_compressed.jpg
901 ms
13_compressed.jpg
865 ms
14_compressed.jpg
789 ms
collect
402 ms
15_compressed.jpg
787 ms
aivee-at-home-2.jpg
796 ms
home-image-01.png
980 ms
home-image-02.png
851 ms
Thermage-1.jpg
858 ms
ultera.jpg
742 ms
Aivee-Glass.jpg
749 ms
Artboard-1.jpg
752 ms
shopping-cart.svg
753 ms
Aivee-Group-Logo-e1595878113109.png
253 ms
ic_menu_24px.svg
255 ms
fcjes.css
71 ms
aivee.ph 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
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
Links do not have a discernible name
aivee.ph best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
aivee.ph 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aivee.ph 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 Aivee.ph 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.
aivee.ph
Open Graph data is detected on the main page of Aivee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: