3.6 sec in total
310 ms
3.1 sec
211 ms
Visit weeke.de now to see the best up-to-date Weeke content and also check out these interesting facts you probably never knew about weeke.de
HOMAG Group is the world's leading manufacturer for woodworking machinery and systems for the wood-processing industry and trades.
Visit weeke.deWe analyzed Weeke.de page load time and found that the first response time was 310 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
weeke.de performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value4.3 s
41/100
25%
Value5.3 s
57/100
10%
Value70 ms
99/100
30%
Value0.155
74/100
15%
Value5.4 s
71/100
10%
310 ms
880 ms
102 ms
321 ms
282 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Weeke.de, 82% (45 requests) were made to Weeke.com and 9% (5 requests) were made to Homaggroupwebapp.homag.de. The less responsive or slowest element that took the longest time to load (962 ms) relates to the external source Weeke.com.
Page size can be reduced by 686.0 kB (32%)
2.1 MB
1.4 MB
In fact, the total size of Weeke.de main page is 2.1 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. 40% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 46.6 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 46.6 kB or 77% of the original size.
Potential reduce by 129.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. Weeke images are well optimized though.
Potential reduce by 339.9 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 339.9 kB or 77% of the original size.
Potential reduce by 169.6 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. Weeke.de needs all CSS files to be minified and compressed as it can save up to 169.6 kB or 85% of the original size.
Number of requests can be reduced by 30 (59%)
51
21
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weeke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
weeke.de
310 ms
VariationRoot.aspx
880 ms
en-en
102 ms
home.aspx
321 ms
controls.css
282 ms
homag.css
382 ms
HtmlEditorCustomStyles.css
193 ms
HTmlEditorcustomstyles.css
196 ms
HtmlEditorTableFormats.css
292 ms
lightbox.css
291 ms
pageLayouts.css
295 ms
rca.css
320 ms
zz1_homag.css
382 ms
core.css
668 ms
init.js
580 ms
non_ie.js
678 ms
Gran1011-65001.css
515 ms
WebResource.axd
481 ms
initNoPresence.js
258 ms
core.js
908 ms
Weltkugel_Zone_1_19084.jpg
440 ms
WebResource.axd
102 ms
Search.gif
105 ms
BHX050_powerTouch_EN_960x350.jpg
390 ms
ho_ecke_ol.jpg
105 ms
ho_ecke_or.jpg
110 ms
ho_ecke_ul.jpg
198 ms
ho_ecke_ur.jpg
203 ms
_Service_EN_188px.jpg
203 ms
ho_bottom_left.gif
212 ms
ho_bottom_right.gif
297 ms
BHX_050_Startbild_Flash_en_19095.jpg
728 ms
Flex5_bearbeitet_21737.jpg
916 ms
Startseite_zufriedene_Mitarbeiter_180px_21124.jpg
918 ms
Termine_21126.jpg
930 ms
ho_top_default.gif
290 ms
ho_bg_navi.jpg
290 ms
Microsite_BHX200_EN_960x350.jpg
478 ms
WEEKE_NIGHT_960x350.jpg
752 ms
TheInnovationsawaken_HOLZ-HANDWERK2016.jpg
662 ms
Proform_Products_Perth_Mark_Anderson_HOMAG_Automation_Storage.jpg
856 ms
Edge%20Commercial_BHX200_Joseph%20Mafrici_slideshow.jpg
861 ms
Mentes%20Joinery_slideshow.jpg
805 ms
ho_verlauf.jpg
584 ms
ho_border_oben.jpg
711 ms
ho_border_left.jpg
877 ms
ho_border_unten.jpg
877 ms
HOMAG_Engineering_EN_188px.jpg
871 ms
Newsletter_EN_188px.jpg
901 ms
Practive_EN_188px.jpg
962 ms
ho_bottom_default.gif
957 ms
ga.js
5 ms
18736
154 ms
__utm.gif
12 ms
18736
256 ms
weeke.de 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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.
weeke.de 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
weeke.de 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weeke.de 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 Weeke.de 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.
weeke.de
Open Graph description is not detected on the main page of Weeke. 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: