2.5 sec in total
176 ms
1.8 sec
525 ms
Visit prym-intimates.com now to see the best up-to-date Prym Intimates content and also check out these interesting facts you probably never knew about prym-intimates.com
As a modern lingerie accessories supplier, our extensive innovation range include featuring accessories such as Bra Hooks & Eye Tapes, Softseal Bra Extender, Bra shoulder Straps, Bra Rings & Slides, B...
Visit prym-intimates.comWe analyzed Prym-intimates.com page load time and found that the first response time was 176 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
prym-intimates.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value11.0 s
0/100
25%
Value11.6 s
4/100
10%
Value5,980 ms
0/100
30%
Value0.001
100/100
15%
Value53.1 s
0/100
10%
176 ms
90 ms
39 ms
17 ms
14 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 66% of them (57 requests) were addressed to the original Prym-intimates.com, 14% (12 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (610 ms) relates to the external source Static.doubleclick.net.
Page size can be reduced by 1.3 MB (23%)
5.8 MB
4.4 MB
In fact, the total size of Prym-intimates.com main page is 5.8 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. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 39.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. This page needs HTML code to be minified as it can gain 16.4 kB, which is 35% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 39.9 kB or 84% of the original size.
Potential reduce by 41.0 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. Prym Intimates images are well optimized though.
Potential reduce by 726.5 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 726.5 kB or 63% of the original size.
Potential reduce by 517.9 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. Prym-intimates.com needs all CSS files to be minified and compressed as it can save up to 517.9 kB or 84% of the original size.
Number of requests can be reduced by 41 (62%)
66
25
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prym Intimates. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
prym-intimates.com
176 ms
51a50e185f84e0b5ffa834cd228d2876-1670999830
90 ms
bootstrap.min.css
39 ms
font-awesome.min.css
17 ms
swiper.css
14 ms
font.css
16 ms
jquery.fancybox.min.css
18 ms
main.css
54 ms
font-awesome.min.css
50 ms
js
283 ms
0364caf9bdf96a7965b5b2282e5ed284-1670997824
125 ms
jquery-2.1.0.min.js
67 ms
swiper.min.js
65 ms
bootstrap.min.js
67 ms
jquery.responsiveTabs.min.js
66 ms
jaaulde-cookies.js
71 ms
main.js
70 ms
jquery.fancybox.min.js
65 ms
js
336 ms
sweetalert.min.js
76 ms
framework.js
71 ms
framework.extras.js
70 ms
framework.extras.css
72 ms
css
89 ms
sweetalert.min.js
46 ms
index.html
146 ms
gxuIMY-GGPo
289 ms
logo.png
162 ms
v-line.png
162 ms
inquiry_cart.gif
162 ms
close-b.png
162 ms
rechap.png
161 ms
Slide-1.jpg
217 ms
Slide-2.jpg
260 ms
Slide-3.jpg
283 ms
Slide-4.jpg
258 ms
Slide-5.jpg
370 ms
5afac45001dcd346089253.jpg
161 ms
5afac47d701b2259237597.jpg
215 ms
5afac48ae3498273868223.jpg
218 ms
5afac49a28c68860745356.jpg
219 ms
5afac4a517307796601486.jpg
222 ms
5afac4b04ad38648572493.jpg
219 ms
sri-lanka.png
258 ms
china.png
257 ms
hong-kong.png
259 ms
indonesia.png
258 ms
united-kingdom.png
259 ms
main.css
145 ms
three.min.js
191 ms
Detector.js
124 ms
OBJLoader.js
124 ms
MTLLoader.js
143 ms
OrbitControls.js
145 ms
main.js
153 ms
drag.svg
150 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
120 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
122 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
149 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
151 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
151 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
153 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
154 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
154 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
151 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
154 ms
fontawesome-webfont.woff
76 ms
fontawesome-webfont.woff
250 ms
www-player.css
19 ms
www-embed-player.js
120 ms
base.js
159 ms
pointer.svg
44 ms
1.mtl
33 ms
1.obj
439 ms
2.jpg
264 ms
1.jpg
35 ms
3.jpg
36 ms
fontawesome-webfont.ttf
381 ms
ad_status.js
610 ms
0o2vSHmH6ApOX27UzDeaY_GD7faOtklBjWYygVKryhI.js
523 ms
embed.js
411 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
49 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
47 ms
fontawesome-webfont.svg
199 ms
id
53 ms
Create
156 ms
prym-intimates.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
prym-intimates.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
Page has valid source maps
prym-intimates.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
Image elements do not have [alt] attributes
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prym-intimates.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Prym-intimates.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.
prym-intimates.com
Open Graph description is not detected on the main page of Prym Intimates. 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: