3.4 sec in total
311 ms
2.8 sec
221 ms
Welcome to homag.de homepage info - get ready to check Homag best content for Russia right away, or after learning these important things about homag.de
Maschinen und Service zur Holzbearbeitung vom führenden Hersteller HOMAG. Anlagen für holzbearbeitende Industrie & Handwerk!
Visit homag.deWe analyzed Homag.de page load time and found that the first response time was 311 ms and then it took 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.
homag.de performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value6.7 s
8/100
25%
Value8.0 s
21/100
10%
Value3,370 ms
2/100
30%
Value0.226
55/100
15%
Value7.4 s
49/100
10%
311 ms
352 ms
105 ms
680 ms
192 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Homag.de, 87% (46 requests) were made to Homag.com and 4% (2 requests) were made to Homaggroupwebapp.homag.de. The less responsive or slowest element that took the longest time to load (936 ms) relates to the external source Homag.com.
Page size can be reduced by 590.6 kB (47%)
1.3 MB
665.0 kB
In fact, the total size of Homag.de 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. 35% of websites need less resources to load. Images take 545.1 kB which makes up the majority of the site volume.
Potential reduce by 45.8 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 45.8 kB or 77% of the original size.
Potential reduce by 23.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. Homag images are well optimized though.
Potential reduce by 351.3 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 351.3 kB or 78% 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. Homag.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 (61%)
49
19
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homag. 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.
homag.de
311 ms
VariationRoot.aspx
352 ms
en-en
105 ms
home.aspx
680 ms
controls.css
192 ms
homag.css
376 ms
HtmlEditorCustomStyles.css
192 ms
HTmlEditorcustomstyles.css
197 ms
HtmlEditorTableFormats.css
289 ms
lightbox.css
282 ms
pageLayouts.css
285 ms
rca.css
287 ms
zz1_homag.css
294 ms
core.css
564 ms
init.js
657 ms
non_ie.js
661 ms
Gran1011-65001.css
580 ms
WebResource.axd
495 ms
initNoPresence.js
287 ms
core.js
936 ms
homag_group_worldwide_teaser_16472.jpg
291 ms
WebResource.axd
97 ms
Search.gif
103 ms
Holz-Handwerk_EN_33507.jpg
383 ms
ho_ecke_ol.jpg
102 ms
ho_ecke_or.jpg
104 ms
ho_ecke_ul.jpg
194 ms
ho_ecke_ur.jpg
197 ms
01_ecoPlus_EN_396px.jpg
292 ms
_Service_EN_188px.jpg
202 ms
ho_bottom_left.gif
290 ms
ho_bottom_right.gif
292 ms
Holzhandwerk_188_100_18259.jpg
573 ms
ho_top_default.gif
285 ms
logo.png
375 ms
ho_bg_navi.jpg
484 ms
TheInnovationsawaken_HOLZ-HANDWERK2016.jpg
548 ms
Sage_Manufacturing_NZ_Homag_KAL310_airTec.jpg
654 ms
02_Mint_Kitchens_KAL310_ZHR340_Canberra_Australia.jpg
641 ms
HOMAG_shaping_change_in_furniture_production.jpg
557 ms
ho_verlauf.jpg
509 ms
ho_border_oben.jpg
554 ms
ho_border_left.jpg
612 ms
ho_border_unten.jpg
640 ms
02_Werkstatt_Workshop_EN_396px.jpg
649 ms
HOMAG_Engineering_EN_188px.jpg
645 ms
Newsletter_EN_188px.jpg
705 ms
Practive_EN_188px.jpg
731 ms
ho_bottom_default.gif
726 ms
ga.js
8 ms
18736
161 ms
__utm.gif
14 ms
18736
265 ms
homag.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.
homag.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
homag.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 Homag.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 Homag.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.
homag.de
Open Graph description is not detected on the main page of Homag. 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: