3.9 sec in total
159 ms
3.2 sec
529 ms
Welcome to peppersq.com homepage info - get ready to check Peppersq best content right away, or after learning these important things about peppersq.com
Welcome to Pepper Sq, your online destination to buy furniture and interior design ideas online. Explore the best in modern European furniture brands, lighting, sofas, beds and more, carefully selecte...
Visit peppersq.comWe analyzed Peppersq.com page load time and found that the first response time was 159 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
peppersq.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value4.0 s
51/100
25%
Value6.0 s
46/100
10%
Value2,760 ms
3/100
30%
Value0
100/100
15%
Value17.4 s
4/100
10%
159 ms
483 ms
51 ms
23 ms
56 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Peppersq.com, 19% (19 requests) were made to Cdn.peppersq.com and 18% (18 requests) were made to Cdn.schema.io. The less responsive or slowest element that took the longest time to load (817 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 353.6 kB (24%)
1.5 MB
1.1 MB
In fact, the total size of Peppersq.com main page is 1.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. 75% 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 879.9 kB which makes up the majority of the site volume.
Potential reduce by 345.4 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 345.4 kB or 75% of the original size.
Potential reduce by 7.9 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. Peppersq images are well optimized though.
Potential reduce by 274 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 30 (32%)
95
65
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Peppersq. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and as a result speed up the page load time.
peppersq.com
159 ms
peppersq.com
483 ms
optimize.js
51 ms
klaviyo.js
23 ms
fender_analytics.739eafc699de20b4c3bb.js
56 ms
static.047f24ade89e4aff54a9.js
59 ms
runtime.de3587c9054d415a20c1.js
17 ms
sharedUtils.a2ead10f1141521a8e3e.js
23 ms
vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js
41 ms
vendors~signup_forms~onsite-triggering.a2030eb5abe19f808c94.js
42 ms
vendors~signup_forms.e707d6d405eecdf67185.js
24 ms
default~signup_forms~onsite-triggering.ddf307d73959ae2a00ef.js
41 ms
signup_forms.5828d30d7aa945da8745.js
40 ms
swiper.min.css
70 ms
css2
53 ms
main.707c8f53ea8c748d9205.js
111 ms
vendors~about~blog~blogPost~careers~cart~confirmOrder~faq~filter~home~klarna~login~order~privacy~pro~55873d35.707c8f53ea8c748d9205.js
476 ms
vendors~cart~filter~home~product~retailerPage.707c8f53ea8c748d9205.js
503 ms
vendors~home~product.707c8f53ea8c748d9205.js
503 ms
home~retailerPage.707c8f53ea8c748d9205.js
484 ms
home.707c8f53ea8c748d9205.js
502 ms
fbevents.js
714 ms
b0ae4701f6c1160a484efe5dba34cb54.jpg
678 ms
ee3ff9335d83db97ba999f062737232d.jpg
678 ms
b28445a37434591bd58741f3ebe01176.jpg
730 ms
6275de9d1e55f358d65c282888a819f2.jpg
729 ms
KFOmCnqEu92Fr1Me5Q.ttf
744 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
764 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
803 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
816 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
817 ms
logger.min.js
653 ms
626 ms
gtm.js
626 ms
products
644 ms
352 ms
js
344 ms
js
342 ms
room-types
445 ms
ddb64d49fbb05a88c2dfb2ce3026b924.jpg
65 ms
07964a234938aa396f88013e119be6d2.jpg
65 ms
5457d6c6a87790a32ff2723108bb494d.jpg
65 ms
7a37bdcef64c20c679a0227eb1ce4e04.jpg
65 ms
3517c18f078fa5cafd5cfbf508a8dc92.png
68 ms
44933b9eb92873dfa214807a3cba7cdb.png
85 ms
d74b0a8bb472ffd325ecd771e4f99a31.jpg
88 ms
0107a70ea6179c72873da4208376cd32.png
86 ms
e3ca63964a413b09dc84d573a60cc1b9.png
86 ms
642595637189354
213 ms
391 ms
core.js
630 ms
js
390 ms
js
387 ms
jsTag
659 ms
analytics.js
370 ms
631 ms
774 ms
6450dcb0828b7100128080f1.webp
688 ms
9e1d581c867a548d24a4646ade7b47ea
667 ms
peppersq.com
550 ms
033a31867e757f55d9c3c339dd61772e
487 ms
e11e78b9a56619a4a482ac06ccf771d8
618 ms
033a31867e757f55d9c3c339dd61772e
615 ms
e11e78b9a56619a4a482ac06ccf771d8
618 ms
9e1d581c867a548d24a4646ade7b47ea
513 ms
e11e78b9a56619a4a482ac06ccf771d8
512 ms
9e1d581c867a548d24a4646ade7b47ea
686 ms
e11e78b9a56619a4a482ac06ccf771d8
609 ms
9e1d581c867a548d24a4646ade7b47ea
619 ms
648fe4aaaab21400125febc7.webp
611 ms
648fe4af51336700122ad523.webp
643 ms
63d557e469a698001377a83f.webp
684 ms
5e4305de38e0631fb25e03d6.webp
685 ms
3af226792d2aab95e93611831a34618f
686 ms
003101feb20899a4a664245288b3bb79
688 ms
6450dcb228366000127f2c04.webp
610 ms
6450dc735f69220012fb97e4.webp
613 ms
6450dc73828b7100128080e4.webp
498 ms
6450dbe85f20720012dc85e4.webp
513 ms
6450dbe8947bec0012a5db70.webp
614 ms
9afb78b8bb0484da81aa8a48bfb08492
641 ms
6450dbcb5f69220012fb97db.webp
617 ms
6450dbcb5cc0200012cfa31b.webp
607 ms
9afb78b8bb0484da81aa8a48bfb08492
608 ms
62055995798e43013dc73cae.webp
610 ms
6205598e798e43013dc72246.webp
642 ms
62055a240266a6013293356e.webp
610 ms
62055a1a11c28d0132b2e057.webp
611 ms
489f5a6fa866f7cf5a90a57b41ce9535
613 ms
6230f052c61273d3dd02fc35da538ae5
614 ms
9edf0e5ef978b6a3e45bdc697e24e10e
680 ms
4965efd1ccdf82cbae15f2d85373f0c3
616 ms
332 ms
collect
242 ms
collect
318 ms
main.cb6ceab7.js
35 ms
101 ms
109 ms
js
100 ms
ga-audiences
126 ms
ct.html
105 ms
peppersq.com
214 ms
peppersq.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.
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
peppersq.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
peppersq.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
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 Peppersq.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 Peppersq.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.
peppersq.com
Open Graph description is not detected on the main page of Peppersq. 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: