10.4 sec in total
315 ms
9.3 sec
751 ms
Welcome to rezorz.com homepage info - get ready to check Rezorz best content right away, or after learning these important things about rezorz.com
Vi brænder for at automatisere grafisk produktion, og vi har stor erfaring med EasyCatalog, Enfocus Switch, Pitstop Pro og workflow
Visit rezorz.comWe analyzed Rezorz.com page load time and found that the first response time was 315 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rezorz.com performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value15.8 s
0/100
25%
Value19.5 s
0/100
10%
Value840 ms
34/100
30%
Value0.127
82/100
15%
Value16.9 s
5/100
10%
315 ms
1841 ms
108 ms
214 ms
36 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 79% of them (74 requests) were addressed to the original Rezorz.com, 14% (13 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Rezorz.com.
Page size can be reduced by 120.2 kB (9%)
1.3 MB
1.2 MB
In fact, the total size of Rezorz.com main page is 1.3 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. 70% of websites need less resources to load. Images take 562.7 kB which makes up the majority of the site volume.
Potential reduce by 110.0 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 110.0 kB or 84% of the original size.
Potential reduce by 1.7 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. Rezorz images are well optimized though.
Potential reduce by 5.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 3.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. Rezorz.com has all CSS files already compressed.
Number of requests can be reduced by 38 (54%)
70
32
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rezorz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
rezorz.com
315 ms
www.rezorz.com
1841 ms
6bsf6.css
108 ms
6bsf6.css
214 ms
css
36 ms
aafj3.css
784 ms
post-7690.css
294 ms
6bsf6.css
489 ms
post-1838.css
294 ms
css
52 ms
aafj3.js
683 ms
6bsf6.js
315 ms
ab3mw.js
397 ms
post-10969.css
394 ms
post-9924.css
413 ms
post-10007.css
494 ms
6bsf6.css
494 ms
index.js
515 ms
index.js
585 ms
script.js
948 ms
page-builder.js
691 ms
effect.min.js
618 ms
script-core.js
689 ms
api.js
39 ms
wp-polyfill-inert.min.js
720 ms
regenerator-runtime.min.js
947 ms
wp-polyfill.min.js
948 ms
index.js
947 ms
slick.min.js
946 ms
active.js
948 ms
script.js
948 ms
webpack.runtime.min.js
949 ms
frontend-modules.min.js
950 ms
waypoints.min.js
949 ms
core.min.js
948 ms
frontend.min.js
1009 ms
underscore.min.js
1093 ms
wp-util.min.js
1095 ms
frontend.min.js
1092 ms
393e41e1-ef02-4c2d-93d8-69c3dfc02a57.js
727 ms
Rezorz-logo-02.png
256 ms
Rezorz_Services_Grafisk_Automatisering_2-1024x576.jpg
259 ms
Rezorz_Services_PIM_2-1024x576.jpg
519 ms
Rezorz_Services_Workflow_2-1024x576.jpg
518 ms
Rezorz_Maskinen-837x1024.png
519 ms
Rezorz_Perfion_solution_partner_logo.png
519 ms
Rezorz_65bit_EasyCatalog_Reseller_Logo-e1712819482406.png
520 ms
Rezorz_Sortering-1024x654.png
549 ms
Rezorz_Tandhjul_Samlet.gif
1219 ms
LOGOS-REZORZ-1-300x300.jpg
552 ms
LOGOS-REZORZ-9_1-300x300.jpg
552 ms
LOGOS-REZORZ-2-300x300.jpg
548 ms
LOGOS-REZORZ-10_3-300x300.jpg
648 ms
LOGOS-REZORZ-3_1-300x300.jpg
650 ms
LOGOS-REZORZ-8_1-300x300.jpg
652 ms
LOGOS-REZORZ-4-300x300.jpg
650 ms
LOGOS-REZORZ-5-300x300.jpg
785 ms
LOGOS-REZORZ-6-300x300.jpg
787 ms
LOGOS-REZORZ-7-300x300.jpg
786 ms
LOGOS-REZORZ-11-300x300.jpg
681 ms
mpDenmark-300x300.jpg
748 ms
Rezorz_logoer-03-300x300.png
748 ms
Rezorz_logoer-02-300x300.png
748 ms
Rezorz_logoer-01-300x300.png
751 ms
Rezorz_logoer-04-300x300.png
845 ms
KFOmCnqEu92Fr1Mu4mxM.woff
60 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
84 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
143 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
174 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
174 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
176 ms
MwQ5bhbm2POE2V9BOw.woff
176 ms
KFOkCnqEu92Fr1Mu51xIIzQ.woff
176 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff
176 ms
KFOjCnqEu92Fr1Mu51TjASc6CsI.woff
177 ms
KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff
177 ms
KFOjCnqEu92Fr1Mu51TzBic6CsI.woff
177 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff
177 ms
fa-solid-900.woff
946 ms
fa-solid-900.woff
847 ms
fa-regular-400.woff
857 ms
fa-regular-400.woff
945 ms
fontawesome-webfont.woff
1068 ms
fa-brands-400.woff
1046 ms
fa-brands-400.woff
1103 ms
recaptcha__en.js
209 ms
ElegantIcons.woff
1002 ms
Perfion_Background_Slide_Web_4-scaled.jpg
1103 ms
Perfion_Background_Slide_Mobile_2-scaled.jpg
1100 ms
EasyCatalog_02.webp
1062 ms
EasyCatalog_web_mobil.webp
1170 ms
Rezorz_Enfocus_Switch_workflow_web.webp
1035 ms
ppms.js
98 ms
ppms.php
368 ms
rezorz.com 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 input fields do not have accessible names
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
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
rezorz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
rezorz.com SEO score
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
DA
DA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rezorz.com 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 Rezorz.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.
rezorz.com
Open Graph data is detected on the main page of Rezorz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: