Tools & Wizards About Us
pepejeans.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pepejeans.com

Pepe Jeans London - Official Website

Page Load Speed

4.8 sec in total

First Response

270 ms

Resources Loaded

3.8 sec

Page Rendered

756 ms

pepejeans.com screenshot

About Website

Visit pepejeans.com now to see the best up-to-date Pepe Jeans content for Spain and also check out these interesting facts you probably never knew about pepejeans.com

Pepe Jeans London new collection. Discover the latest trends in fashion and accessories for women, men and kids.

Visit pepejeans.com

Key Findings

We analyzed Pepejeans.com page load time and found that the first response time was 270 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

pepejeans.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value4,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

Network Requests Diagram

pepejeans.com

270 ms

pepejeans.com

359 ms

425 ms

gtm.js

141 ms

fs.js

52 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 36% of them (33 requests) were addressed to the original Pepejeans.com, 18% (17 requests) were made to Webservices.global-e.com and 9% (8 requests) were made to Cmp.inmobi.com. The less responsive or slowest element that took the longest time to load (525 ms) relates to the external source Cmp.inmobi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 166.3 kB (6%)

Content Size

2.7 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pepejeans.com main page is 2.7 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. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 131.4 kB

  • Original 163.1 kB
  • After minification 162.4 kB
  • After compression 31.7 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 131.4 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 17.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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. Pepe Jeans images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 17.5 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 1.2 MB

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.

CSS Optimization

-0%

Potential reduce by 48 B

  • Original 240.9 kB
  • After minification 240.9 kB
  • After compression 240.8 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. Pepejeans.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (61%)

Requests Now

75

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pepe Jeans. 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 from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pepejeans.com

pepejeans.com

270 ms

pepejeans.com

pepejeans.com

359 ms

425 ms

gtm.js

gtm.js

141 ms

fs.js

fs.js

52 ms

entry.js

entry.js

135 ms

styles.css

styles.css

72 ms

photoswipe.min.css

photoswipe.min.css

107 ms

jquery.min.js

jquery.min.js

118 ms

paypal.css

paypal.css

43 ms

flags.css

flags.css

402 ms

flags.css

flags.css

69 ms

styles.css

styles.css

66 ms

globaleScriptLoader.js

globaleScriptLoader.js

66 ms

globaleCountrySwitcher.js

globaleCountrySwitcher.js

134 ms

enterprise.js

enterprise.js

148 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

133 ms

jquery-accessible-nav__custom.js

jquery-accessible-nav__custom.js

73 ms

popper.min.js

popper.min.js

72 ms

tooltip.min.js

tooltip.min.js

72 ms

monetate.js

monetate.js

72 ms

player.js

player.js

164 ms

app.js

app.js

144 ms

checkout.js

checkout.js

147 ms

paypalUtils.js

paypalUtils.js

128 ms

paypalSG.js

paypalSG.js

129 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

128 ms

dwac-21.7.js

dwac-21.7.js

127 ms

gretel.min.js

gretel.min.js

143 ms

globale.merchant.client.js

globale.merchant.client.js

265 ms

sprite-icons-black.svg

sprite-icons-black.svg

117 ms

icon-right-arrow-white.svg

icon-right-arrow-white.svg

113 ms

success-icon.svg

success-icon.svg

200 ms

error-close.svg

error-close.svg

201 ms

ApercuPro-Regular.otf

ApercuPro-Regular.otf

60 ms

ApercuPro-Black.otf

ApercuPro-Black.otf

58 ms

ApercuPro-Bold.otf

ApercuPro-Bold.otf

142 ms

icons.woff

icons.woff

108 ms

ApercuPro-Medium.otf

ApercuPro-Medium.otf

116 ms

us.svg

us.svg

116 ms

recaptcha__en.js

recaptcha__en.js

123 ms

choice.js

choice.js

525 ms

print.css

print.css

96 ms

welcome

welcome

173 ms

pptm.js

pptm.js

206 ms

fallback

fallback

191 ms

2404-hp-highlighted-categories-x3-XXXL-W.jpg

2404-hp-highlighted-categories-x3-XXXL-W.jpg

65 ms

2404-hp-highlighted-categories-x3-XXXL-M.jpg

2404-hp-highlighted-categories-x3-XXXL-M.jpg

47 ms

2404-hp-highlighted-categories-x3-XXXL-K.jpg

2404-hp-highlighted-categories-x3-XXXL-K.jpg

45 ms

fallback__ltr.css

fallback__ltr.css

40 ms

ts

ts

435 ms

css

css

126 ms

cmp2-polyfilled.js

cmp2-polyfilled.js

21 ms

cmp-list.json

cmp-list.json

13 ms

logger

logger

462 ms

logo_48.png

logo_48.png

35 ms

cmp2ui-en.js

cmp2ui-en.js

32 ms

vendor-list-trimmed-v1.json

vendor-list-trimmed-v1.json

12 ms

google-atp-list.json

google-atp-list.json

110 ms

vendor-list.json

vendor-list.json

257 ms

logo_full.svg

logo_full.svg

130 ms

api.cmp.inmobi.com

api.cmp.inmobi.com

491 ms

geoip

geoip

29 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

111 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

113 ms

set

set

214 ms

freeShippingBanner

freeShippingBanner

260 ms

set

set

273 ms

US

US

34 ms

WriteLog

WriteLog

192 ms

prefetcher.js

prefetcher.js

26 ms

PrefetcherProcess

PrefetcherProcess

31 ms

checkoutv2_top.js

checkoutv2_top.js

29 ms

checkoutv2_bottom.js

checkoutv2_bottom.js

112 ms

secured.js

secured.js

49 ms

spritesheet.png

spritesheet.png

109 ms

content_bootstrap_cssRtl.css

content_bootstrap_cssRtl.css

86 ms

content_bootstrap_css.css

content_bootstrap_css.css

70 ms

CheckoutSkin

CheckoutSkin

297 ms

loader4.gif

loader4.gif

127 ms

horizontal_loader.gif

horizontal_loader.gif

102 ms

secure_spritesheet.png

secure_spritesheet.png

114 ms

sprite_US.png

sprite_US.png

80 ms

main.js

main.js

127 ms

btnClose.png

btnClose.png

91 ms

Logo.png

Logo.png

70 ms

Apercu-Bold.ttf

Apercu-Bold.ttf

152 ms

Apercu-Regular.ttf

Apercu-Regular.ttf

72 ms

set

set

132 ms

pebble

pebble

30 ms

HelveticaNeueW01-75Bold.woff

HelveticaNeueW01-75Bold.woff

64 ms

helveticaneueltstd-roman.woff

helveticaneueltstd-roman.woff

26 ms

Accessibility Review

pepejeans.com accessibility score

87

Accessibility Issues

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

High

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pepejeans.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pepejeans.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8/

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pepejeans.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 Pepejeans.com main page’s claimed encoding is utf-8/. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

pepejeans.com

Open Graph description is not detected on the main page of Pepe Jeans. 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: