Tools & Wizards About Us
primark.at screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

primark.at

Mode, Home & Beauty | Primark

Page Load Speed

3 sec in total

First Response

334 ms

Resources Loaded

2.1 sec

Page Rendered

563 ms

primark.at screenshot

About Website

Visit primark.at now to see the best up-to-date Primark content and also check out these interesting facts you probably never knew about primark.at

Entdecke mit Primark die neuesten Modetrends! Jeden Tag neue Damen- und Herrenbekleidung im Store. Plane deinen nächsten Einkauf jetzt online!

Visit primark.at

Key Findings

We analyzed Primark.at page load time and found that the first response time was 334 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

primark.at performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value19.4 s

0/100

10%

TBT (Total Blocking Time)

Value6,080 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.106

88/100

15%

TTI (Time to Interactive)

Value23.3 s

1/100

10%

Network Requests Diagram

primark.at

334 ms

de-de

1264 ms

api_static.js

34 ms

api_dynamic.js

39 ms

OtAutoBlock.js

128 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Primark.at, 47% (20 requests) were made to Primark.com and 33% (14 requests) were made to Primedia.primark.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Primark.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 860.1 kB (13%)

Content Size

6.4 MB

After Optimization

5.5 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Primark.at main page is 6.4 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 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 676.7 kB

  • Original 783.6 kB
  • After minification 783.6 kB
  • After compression 106.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 676.7 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 45.5 kB

  • Original 5.4 MB
  • After minification 5.3 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. Primark images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 137.9 kB

  • Original 241.7 kB
  • After minification 241.0 kB
  • After compression 103.8 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 137.9 kB or 57% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (66%)

Requests Now

38

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Primark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

primark.at

primark.at

334 ms

de-de

de-de

1264 ms

api_static.js

api_static.js

34 ms

api_dynamic.js

api_dynamic.js

39 ms

OtAutoBlock.js

OtAutoBlock.js

128 ms

otSDKStub.js

otSDKStub.js

167 ms

evergage.min.js

evergage.min.js

35 ms

f3e212c46c698cf6.css

f3e212c46c698cf6.css

25 ms

447c4556f3bf7bd6.css

447c4556f3bf7bd6.css

35 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

34 ms

webpack-e10f1a15d624ccf6.js

webpack-e10f1a15d624ccf6.js

30 ms

framework-a4c46ec9f694b7af.js

framework-a4c46ec9f694b7af.js

116 ms

main-7c4a3c722baff7f3.js

main-7c4a3c722baff7f3.js

116 ms

_app-287982229fa1ca59.js

_app-287982229fa1ca59.js

135 ms

fec483df-d4d590ce7033d5d7.js

fec483df-d4d590ce7033d5d7.js

121 ms

6261-6647c61b58cd8880.js

6261-6647c61b58cd8880.js

135 ms

1498-a4c8288738a5b0a8.js

1498-a4c8288738a5b0a8.js

124 ms

1826-3c6957a05ff11a3e.js

1826-3c6957a05ff11a3e.js

134 ms

4313-02de447ee4c6ed5c.js

4313-02de447ee4c6ed5c.js

138 ms

index-8764ae615ae7aa3e.js

index-8764ae615ae7aa3e.js

146 ms

_buildManifest.js

_buildManifest.js

225 ms

_ssgManifest.js

_ssgManifest.js

226 ms

gtm.js

gtm.js

144 ms

PrimarkPride24

PrimarkPride24

111 ms

WK38%20-%20Germany%20ONLY%20Landing%20Page%20banner13

WK38%20-%20Germany%20ONLY%20Landing%20Page%20banner13

62 ms

Wk%2038-%20Womens%20-%20GERMANY%204

Wk%2038-%20Womens%20-%20GERMANY%204

389 ms

Wk%2036%20-%20Kids%20-%20Landing%20Tile%20-02

Wk%2036%20-%20Kids%20-%20Landing%20Tile%20-02

59 ms

Wk%2036%20-%20Baby%20-%20Landing%20Tile%20-02

Wk%2036%20-%20Baby%20-%20Landing%20Tile%20-02

60 ms

Wk%2036%20-%20Home%20%20-%20Landing%20Tile

Wk%2036%20-%20Home%20%20-%20Landing%20Tile

65 ms

Wk%2036%20-%20Men%20%20-%20Landing%20Tile%20-02

Wk%2036%20-%20Men%20%20-%20Landing%20Tile%20-02

62 ms

Wk%2036%20-%20Beauty%20%20-%20Landing%20Tile%20-%20TIER%202_3%20-%20campaign_1

Wk%2036%20-%20Beauty%20%20-%20Landing%20Tile%20-%20TIER%202_3%20-%20campaign_1

66 ms

ic_pinterest

ic_pinterest

62 ms

ic_facebook

ic_facebook

62 ms

ic_instagram

ic_instagram

64 ms

ic_youtube

ic_youtube

66 ms

ic_tiktok

ic_tiktok

67 ms

Deutschland

Deutschland

67 ms

9b0023df-a911-478c-9d3a-88ba02ac0580.json

9b0023df-a911-478c-9d3a-88ba02ac0580.json

59 ms

location

location

86 ms

PrimarkBasis-Bold.woff

PrimarkBasis-Bold.woff

36 ms

PrimarkBasis-Regular.woff

PrimarkBasis-Regular.woff

181 ms

arial-black-woff.woff

arial-black-woff.woff

15 ms

USYAg1Vjk

USYAg1Vjk

33 ms

Accessibility Review

primark.at accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

primark.at best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

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

primark.at SEO score

100

Search Engine Optimization Advices

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Primark.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Primark.at 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.

Social Sharing Optimization

primark.at

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