4.7 sec in total
93 ms
1.6 sec
2.9 sec
Visit ultacosme.com now to see the best up-to-date Ulta Cosme content and also check out these interesting facts you probably never knew about ultacosme.com
Shop top beauty brands & new arrivals at Ulta Beauty. Join ULTAmate Rewards. Free store pickup & curbside available.
Visit ultacosme.comWe analyzed Ultacosme.com page load time and found that the first response time was 93 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ultacosme.com performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value21.0 s
0/100
25%
Value15.6 s
0/100
10%
Value14,640 ms
0/100
30%
Value0.444
21/100
15%
Value28.2 s
0/100
10%
93 ms
215 ms
48 ms
31 ms
26 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ultacosme.com, 91% (105 requests) were made to Ulta.com and 5% (6 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (705 ms) relates to the external source Ulta.com.
Page size can be reduced by 1.3 MB (83%)
1.6 MB
273.2 kB
In fact, the total size of Ultacosme.com main page is 1.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. HTML takes 1.5 MB which makes up the majority of the site volume.
Potential reduce by 1.3 MB
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 1.3 MB or 90% of the original size.
Potential reduce by 45 B
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.
Number of requests can be reduced by 103 (94%)
109
6
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ulta Cosme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 49 to 1 for CSS and as a result speed up the page load time.
ultacosme.com
93 ms
www.ulta.com
215 ms
ruxitagentjs_ICA27NVfghjqrux_10285240307101407.js
48 ms
otSDKStub.js
31 ms
main.b1800392.css
26 ms
MainWrapper-MainWrapper.5a20188b.chunk.css
28 ms
72726.c7a06021.chunk.css
30 ms
GlobalMessagingBar-GlobalMessagingBar.5756c8c9.chunk.css
44 ms
VideoBanner-VideoBanner.740c125c.chunk.css
103 ms
17863.d509306d.chunk.css
88 ms
PromotionalRail-PromotionalRail.8d537dbe.chunk.css
45 ms
65334.3ced1722.chunk.css
97 ms
ImageBackgroundCard-ImageBackgroundCard.3a290194.chunk.css
107 ms
56222.72cf9e9d.chunk.css
118 ms
41278.98863804.chunk.css
116 ms
LargeDealCard-LargeDealCard.0b764c52.chunk.css
175 ms
LargeDealRail-LargeDealRail.821501b3.chunk.css
140 ms
ArticleRowStackedCompact-ArticleRowStackedCompact.737a2d1c.chunk.css
111 ms
ArticleRowStackedLarge-ArticleRowStackedLarge.9da795fb.chunk.css
127 ms
67764.4f7380e2.chunk.css
120 ms
71521.a7f90c8f.chunk.css
131 ms
BlockMessage-BlockMessage.115d3dff.chunk.css
153 ms
77086.f849641d.chunk.css
145 ms
ProductCard-ProductCard.db4792b5.chunk.css
134 ms
61792.fd705d23.chunk.css
148 ms
ProductRail-ProductRail.2f90b736.chunk.css
142 ms
UltamateRewardsOffers-UltamateRewardsOffers.632c035d.chunk.css
156 ms
52325.71c5367e.chunk.css
161 ms
CategoryNav-CategoryNav.596c7aa9.chunk.css
298 ms
HalfImageHero-HalfImageHero.82a649b2.chunk.css
196 ms
68822.8a88a614.chunk.css
157 ms
RegularPromotedCompactCards-RegularPromotedCompactCards.1d15eefe.chunk.css
166 ms
TopBar-TopBar.9b86f3cc.chunk.css
166 ms
50350.a75f0bce.chunk.css
167 ms
ValueMessaging-ValueMessaging.ed828b7f.chunk.css
184 ms
74438.9dd9d309.chunk.css
175 ms
UtilityLinks-UtilityLinks.e1e9f0fe.chunk.css
181 ms
PrimaryBar-PrimaryBar.5438d88a.chunk.css
184 ms
PrimaryLinks-PrimaryLinks.cdb58635.chunk.css
198 ms
NavigationOverlay-NavigationOverlay.c3387f8a.chunk.css
197 ms
NavigationLinksGroup-NavigationLinksGroup.0fb950a0.chunk.css
218 ms
71.23f139a9.chunk.css
193 ms
NavigationLinksSubGroup-NavigationLinksSubGroup.838d9542.chunk.css
199 ms
f698a2e0-43cc-4586-bb2b-5231019638b9.json
65 ms
NavigationOverlayFeaturedContent-NavigationOverlayFeaturedContent.7cef89a1.chunk.css
192 ms
42930.1d772d66.chunk.css
146 ms
SearchL-SearchL.c8d12c20.chunk.css
159 ms
FavoritesUtilityLink-FavoritesUtilityLink.562160f0.chunk.css
184 ms
BagIcon-BagIcon.44601341.chunk.css
174 ms
Footer-Footer.1d604986.chunk.css
140 ms
FooterNavLinkGroup-FooterNavLinkGroup.00a3c7ea.chunk.css
164 ms
MediaIcons-MediaIcons.80ab05f9.chunk.css
177 ms
AppDetails-AppDetails.771fcf8a.chunk.css
218 ms
location
69 ms
SignUpNews-SignUpNews.8293388d.chunk.css
171 ms
main.9f83d497.js
176 ms
MainWrapper-MainWrapper.b22a8453.chunk.js
164 ms
20156.d9b88ab4.chunk.js
169 ms
GlobalMessagingBar-GlobalMessagingBar.cd1c6e10.chunk.js
647 ms
VerticalSlot-VerticalSlot.40f3484f.chunk.js
161 ms
48819.8018d2ec.chunk.js
619 ms
50111.a45c9a28.chunk.js
617 ms
VideoBanner-VideoBanner.94d13091.chunk.js
618 ms
49916.3fe65642.chunk.js
613 ms
PromotionalRail-PromotionalRail.38e11cf9.chunk.js
625 ms
ImageBackgroundCard-ImageBackgroundCard.eab4d073.chunk.js
611 ms
FeaturedPromotedCompactCard-FeaturedPromotedCompactCard.b478ce37.chunk.js
621 ms
41278.c3c7ad43.chunk.js
617 ms
LargeDealCard-LargeDealCard.b403289d.chunk.js
617 ms
LargeDealRail-LargeDealRail.999a8fd6.chunk.js
612 ms
ArticleRowStackedCompact-ArticleRowStackedCompact.b88269a3.chunk.js
705 ms
ArticleRowStackedLarge-ArticleRowStackedLarge.00ad1fed.chunk.js
675 ms
39440.5cb0b32b.chunk.js
667 ms
BlockMessage-BlockMessage.e6af31bb.chunk.js
673 ms
otBannerSdk.js
12 ms
ProductCard-ProductCard.5bd4921c.chunk.js
659 ms
en.json
33 ms
ProductRail-ProductRail.659aad1f.chunk.js
639 ms
CuratedProductRail-CuratedProductRail.5acf9458.chunk.js
643 ms
71877.f14b1666.chunk.js
626 ms
CategoryNav-CategoryNav.52dbc9f9.chunk.js
621 ms
HalfImageHero-HalfImageHero.e51b7a3d.chunk.js
643 ms
RegularPromotedCompactCards-RegularPromotedCompactCards.2ed21687.chunk.js
611 ms
DataCaptureEvent-DataCaptureEvent.14c261ee.chunk.js
602 ms
WebpageMetaData-WebpageMetaData.79d8d782.chunk.js
599 ms
otCenterRounded.json
29 ms
otPcTab.json
33 ms
46940.a3566ad6.chunk.js
602 ms
50452.d12e78bc.chunk.js
599 ms
ValueMessaging-ValueMessaging.2d908ff9.chunk.js
601 ms
StateWrapper-StateWrapper.c2236952.chunk.js
654 ms
UtilityLinks-UtilityLinks.73aea4f5.chunk.js
589 ms
PrimaryBar-PrimaryBar.648a9152.chunk.js
590 ms
PrimaryLinks-PrimaryLinks.cdd8d332.chunk.js
649 ms
NavigationOverlay-NavigationOverlay.94aeeae5.chunk.js
588 ms
NavigationLinksGroup-NavigationLinksGroup.357eb38f.chunk.js
581 ms
NavigationLinksSubGroup-NavigationLinksSubGroup.df532940.chunk.js
584 ms
NavigationOverlayFeaturedContent-NavigationOverlayFeaturedContent.6faa1304.chunk.js
582 ms
A9LXT-5LNZ2-Z7AK2-E456Q-UFJ84
435 ms
SearchL-SearchL.f65b9f59.chunk.js
123 ms
FavoritesUtilityLink-FavoritesUtilityLink.56c89b7c.chunk.js
130 ms
BagIcon-BagIcon.94ae02ce.chunk.js
129 ms
NavigationLink-NavigationLink.e08ced5d.chunk.js
128 ms
Footer-Footer.2f3c0c4a.chunk.js
185 ms
ColumnContainer-ColumnContainer.dce3d46c.chunk.js
181 ms
FooterNavLinkGroup-FooterNavLinkGroup.bb840526.chunk.js
163 ms
MediaIcons-MediaIcons.b58b8446.chunk.js
338 ms
43901.1bc6a982.chunk.js
167 ms
AppDetails-AppDetails.51c1a633.chunk.js
172 ms
SignUpNews-SignUpNews.0339a369.chunk.js
339 ms
CircularStd-Book.9048137056e4347dbbd5.otf
332 ms
CircularStd-Medium.9ffafeddf192e8c8a111.otf
110 ms
CircularStd-Bold.5c4514a8399ec0064b9b.otf
268 ms
ChronicleDeck-Roman.3fd0b10255f293e4dd6b.otf
265 ms
config.json
47 ms
ultacosme.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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
ultacosme.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
Page has valid source maps
ultacosme.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 Ultacosme.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 Ultacosme.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.
ultacosme.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: