3.2 sec in total
423 ms
2.4 sec
450 ms
Welcome to pecani.dk homepage info - get ready to check Pecani best content right away, or after learning these important things about pecani.dk
Hos Guldsmed Pecani har vi vores service i top. Du kan se vores store udvalg af smykker og ure ved at klikke dig ind på vores website lige her! Vi har landsdækkende bytteservice i mere end 300 butikke...
Visit pecani.dkWe analyzed Pecani.dk page load time and found that the first response time was 423 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
pecani.dk performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value10.7 s
0/100
25%
Value8.5 s
17/100
10%
Value1,870 ms
9/100
30%
Value0
100/100
15%
Value14.2 s
9/100
10%
423 ms
97 ms
192 ms
204 ms
202 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 84% of them (66 requests) were addressed to the original Pecani.dk, 5% (4 requests) were made to Woomio.com and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (869 ms) relates to the external source Secure.viabill.com.
Page size can be reduced by 846.3 kB (47%)
1.8 MB
938.8 kB
In fact, the total size of Pecani.dk main page is 1.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. 60% of websites need less resources to load. Images take 816.3 kB which makes up the majority of the site volume.
Potential reduce by 78.2 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 78.2 kB or 86% of the original size.
Potential reduce by 86.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. Obviously, Pecani needs image optimization as it can save up to 86.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 569.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 569.8 kB or 77% of the original size.
Potential reduce by 111.4 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. Pecani.dk needs all CSS files to be minified and compressed as it can save up to 111.4 kB or 83% of the original size.
Number of requests can be reduced by 40 (52%)
77
37
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pecani. 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.
www.pecani.dk
423 ms
flexslider.css
97 ms
styles.css
192 ms
widgets.css
204 ms
styles.css
202 ms
ajaxcartpopup.css
203 ms
prototype.js
294 ms
ccard.js
206 ms
validation.js
286 ms
builder.js
317 ms
effects.js
316 ms
dragdrop.js
319 ms
controls.js
319 ms
slider.js
379 ms
js.js
390 ms
form.js
401 ms
menu.js
398 ms
translate.js
399 ms
cookies.js
401 ms
jquery-1.6.2.js
659 ms
jquery.no.conflict.js
486 ms
ajaxcartpopup.js
492 ms
readmore.js
494 ms
ro.js
100 ms
bootstrap-responsive.css
494 ms
jquery.min.js
92 ms
common.js
500 ms
jquery.flexslider.js
580 ms
flexslider.css
583 ms
cloud-zoom.1.0.2.min.js
588 ms
cloud-zoom.css
590 ms
superfish.js
595 ms
superfish.css
704 ms
superfish-vertical.css
705 ms
multiple-accordion-1.js
706 ms
ro.js
79 ms
logo_pecani.png
106 ms
cart.png
106 ms
gratis_fragt.png
105 ms
phone.png
107 ms
daniel-wellington-slider.jpg
195 ms
fie-carlsson-slider.jpg
107 ms
Slider_Barned_b_2.0.jpg
190 ms
gaia-slider.jpg
284 ms
Skagen_ure_Pecani_Slider.jpg
296 ms
guldsmed-torben-edens.jpg
195 ms
222322_3.jpg
199 ms
oliven.jpg
283 ms
lavendel.jpg
297 ms
seiko-sxgm38.jpg
295 ms
seiko_astron.jpg
495 ms
gr_.png
566 ms
gj_cascade.jpg
376 ms
festina_gul.jpg
492 ms
festina.jpg
587 ms
c001_217_36_297_10_certina.jpg
395 ms
certina.jpg
471 ms
certina_12.jpg
526 ms
loading.gif
565 ms
ga.js
27 ms
header.png
583 ms
loader.gif
585 ms
sprites.png
616 ms
menu.png
629 ms
__utm.gif
15 ms
loading.gif
584 ms
span4contentbg.jpg
618 ms
footer_ico.png
597 ms
footer-links.png
596 ms
kortlogoer.png
614 ms
0Knb0M2pPtk%3D
869 ms
0Knb0M2pPtk%3D
757 ms
cid.aspx
363 ms
iframe
356 ms
json
64 ms
injecter
93 ms
tracker.js
11 ms
print.css
97 ms
jquery.min.js
20 ms
pecani.dk 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 IDs are not unique
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Some elements have a [tabindex] value greater than 0
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
pecani.dk 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pecani.dk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
DA
DA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pecani.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it matches the claimed language. Our system also found out that Pecani.dk 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.
pecani.dk
Open Graph description is not detected on the main page of Pecani. 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: