7.2 sec in total
1.8 sec
5.3 sec
137 ms
Visit potterybarn.ae now to see the best up-to-date Pottery Barn content for United Arab Emirates and also check out these interesting facts you probably never knew about potterybarn.ae
Shop online from our home decor products & accessories at the best prices. Find luxury home furniture, bathroom & outdoor furniture at Pottery Barn UAE.
Visit potterybarn.aeWe analyzed Potterybarn.ae page load time and found that the first response time was 1.8 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
potterybarn.ae performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value37.8 s
0/100
25%
Value19.1 s
0/100
10%
Value10,050 ms
0/100
30%
Value0.833
4/100
15%
Value33.7 s
0/100
10%
1841 ms
416 ms
160 ms
60 ms
36 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 35% of them (22 requests) were addressed to the original Potterybarn.ae, 13% (8 requests) were made to Fonts.gstatic.com and 10% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Potterybarn.ae.
Page size can be reduced by 120.9 kB (9%)
1.3 MB
1.2 MB
In fact, the total size of Potterybarn.ae main page is 1.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. 80% 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 88.3 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 88.3 kB or 78% of the original size.
Potential reduce by 32.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. This website has mostly compressed JavaScripts.
Potential reduce by 12 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. Potterybarn.ae has all CSS files already compressed.
Number of requests can be reduced by 36 (72%)
50
14
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pottery Barn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
potterybarn.ae
1841 ms
416 ms
gtm.js
160 ms
datadog-logs-v4.js
60 ms
css_ydDFHWqI3tw5q8XrATTLT5lkeAnmuFJmaAlKIpQCB7U.css
36 ms
css_B9sPkk0NO_QC8AKuc9vUjTRgFX13VgHSm7qhGb5t-Us.css
39 ms
css2
48 ms
css_uX_GyqVkpK2z70R1J4pIwdKvpCedm5tUwFq1aiey-8E.css
69 ms
js_G0gCFBfKBJOjYaY7Ev52H8kHpv8bn6KSMozsumw989U.js
50 ms
loader.js
37 ms
axios.min.js
553 ms
react.production.min.js
42 ms
react-dom.production.min.js
562 ms
js_gmUlJEn1MFtbn0zQq-9V6t2maGFOteEOT1-1uO9FDMg.js
151 ms
modern_browser_detector.js
64 ms
js_nbjddFBEB-IH9NR7LOj8LkY_enNiO9sdYCPWTI3H808.js
149 ms
sprinklr.min.js
593 ms
js_0n5TZMqzmHWfeIWGNkNG2rfGhkYZbr2XP8xCP_T_eYE.js
151 ms
details-polyfill.js
150 ms
js_TySe-85fawkqKjNE6656O-EWoH1LRZaLbI8CtYpJwPY.js
357 ms
v84a3a4012de94ce1a686ba8c167c359c1696973893317
149 ms
site-logo.svg
133 ms
card-mastercard.svg
195 ms
card-visa.svg
194 ms
DED-Permission-PB.png
746 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf
196 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4nY1M2xYkS.ttf
285 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4nY1M2xYkS.ttf
418 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4nY1M2xYkS.ttf
451 ms
search-insights@2.2.1
362 ms
js
124 ms
js
202 ms
analytics.js
300 ms
ld.js
356 ms
exponea.min.js
621 ms
js
289 ms
events.js
566 ms
scevent.min.js
564 ms
hgofl48per
346 ms
js
249 ms
SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-W1ToLQ-GokM.ttf
491 ms
SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hL4-W1ToLQ-GokM.ttf
490 ms
SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hD45W1ToLQ-GokM.ttf
488 ms
SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5W1ToLQ-GokM.ttf
490 ms
alshaya-icons.woff
73 ms
collect
666 ms
collect
230 ms
collect
273 ms
clarity.js
110 ms
v1.js
60 ms
201 ms
fbevents.js
123 ms
bQCCixN0lvnQB3kb4IhR.js
202 ms
1_0
105 ms
syncframe
99 ms
main.MTU3YmJkODI0MA.js
73 ms
activityi;src=9745598;type=homep0;cat=globa0;ord=1360337387863;npa=0;auiddc=2035051059.1707193325;u1=GA1.1.537273629.1707193325;u2=https%3A%2F%2Fwww.potterybarn.ae%2Fen%2F;u3=Guest%20User;u4=undefined;u5=en;u6=home%20page;u7=United%20Arab%20Emirates;u8=AED;u9=New%20Customer;pscdl=noapi;gtm=45He41v0v810840673za200;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.potterybarn.ae%2Fen%2F
158 ms
collect
131 ms
ga-audiences
43 ms
event
333 ms
src=9745598;type=homep0;cat=globa0;ord=1360337387863;npa=0;auiddc=*;u1=GA1.1.537273629.1707193325;u2=https%3A%2F%2Fwww.potterybarn.ae%2Fen%2F;u3=Guest%20User;u4=undefined;u5=en;u6=home%20page;u7=United%20Arab%20Emirates;u8=AED;u9=New%20Customer;pscdl=noapi;gtm=45He41v0v810840673za200;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.potterybarn.ae%2Fen%2F
88 ms
33 ms
potterybarn.ae accessibility score
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-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
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
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.
potterybarn.ae 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
Missing source maps for large first-party JavaScript
potterybarn.ae SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Potterybarn.ae 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 Potterybarn.ae 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.
potterybarn.ae
Open Graph description is not detected on the main page of Pottery Barn. 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: