Lime render is a traditional building material used for centuries to protect and decorate external walls. Comprised of lime, water, and an aggregate such as sand, lime render allows buildings to breathe, reducing dampness and improving indoor air quality. Its flexibility makes it especially suitable for older buildings that may move or settle over time. As the new EWI Pro Heritage Lime Range recently landed at the EWI Store, we thought it would be a good time to discuss how to apply it. Therefore, if you’re considering applying lime render to a building, here’s a step-by-step guide to help you achieve the best results.
Modern lime render systems have evolved significantly from the traditional lime ranges that required onsite slaking. Traditional lime rendering involved quicklime, which had to be carefully slaked with water to create lime putty. This process could be hazardous due to the exothermic reaction of slaking. This lime putty would then be mixed with aggregates to create the mortar for rendering. The process demanded a deep understanding of the material characteristics and careful attention to achieve the right consistency and workability of the mortar for application.
In contrast, modern lime render systems, such as EWI-747 Lime Render and EWI-748 Lime Basecoat, offer pre-mixed solutions incorporating technological and material science advances. These modern systems often include hydraulic lime, which sets through hydration and can cure even in the presence of water, making them more versatile and easier to use compared to non-hydraulic lime, which is traditionally used. Modern lime renders can be directly applied without onsite slaking, reducing preparation time and making the application process safer and more efficient.
Before applying lime render, it’s crucial to prepare the surface properly. This involves removing any loose or damaged material, dust, and vegetation. If you’re applying render to a previously painted or rendered surface, you must strip it back to the bare wall. The surface should be dampened before application to ensure the render adheres properly and to reduce the risk of it drying too quickly, which can cause cracking.
For both EWI-747 Lime Render and EWI-748 Lime Basecoat, precise mixing with water is crucial to achieve the desired consistency and performance. The EWI-747 Lime Render should be mixed exclusively with water at a rate of 4-5 litres per bag, ensuring a homogeneous consistency free of lumps for 3 to 5 minutes. Exceeding the recommended water quantity can compromise the mortar’s mechanical resistance and lead to cracking. The mixture must be used within 60 minutes of kneading.
Similarly, the EWI-748 Lime Basecoat requires mixing with water only at a rate of 4.5-5 litres per bag. Pour the water into a bucket and gradually add the product, mixing to achieve a lump-free, homogeneous consistency for 3 to 5 minutes. Over-watering the mix could result in a loss of mechanical strength and potential cracking. Once mixed, the basecoat has a longer working time, allowing for adjustments during application.
For both products, an electric or concrete mixer is recommended for large quantities to ensure an even mix. Proper mixing is essential for optimal application and durability of the lime render system.
The application process for EWI-747 Lime Render and EWI-748 Lime Basecoat is designed to ensure optimal coverage and performance on various substrates. Understanding each product’s specific techniques and considerations will help achieve a durable, aesthetically pleasing finish.
The EWI-747 Lime Render can be applied manually using a trowel or sprayed with an automatic plastering machine, catering to traditional and modern application methods. Applying the render to a usual thickness of 4 to 10 mm is recommended for effective results. If a greater thickness is required, exceeding 10 mm, it should be applied in two or more layers, with each layer applied before the previous one has fully hardened. This method helps to avoid cracking and ensures a uniform thickness throughout the application area. Once applied, the surface should be floated to achieve the desired finish, be it smooth or textured, depending on the project requirements.
The EWI-748 Lime Basecoat, designed for both interior and exterior masonry works, offers a flexible base layer for subsequent finishes or as a standalone application where a rustic or refined texture is desired. The basecoat should be spread to a thickness of 4 to 10 mm, and for applications requiring thicknesses greater than 10 mm, it’s advisable to apply in two or more coats. Like the lime render, each coat should be applied before the previous one has fully hardened to ensure proper adhesion and prevent delamination.
For the adhesion of insulation boards, a perimeter cordon of 6 to 10 cm width and 2.5 to 5 cm thickness should be applied on the plate, with the inside of the cordon filled with two or more sticks of 8 to 10 cm depending on the plate size. The mortar must cover at least 40% of the panel surface to ensure effective insulation adhesion. When working on supports with very good planimetry, it’s possible to apply the mortar directly on the support and the insulating panels using a 10mm x 10mm notched trowel, a method known as double glueing.
Regularisation of the insulating panels with mesh involves applying a combed coat with a 6-8 mm notched trowel, laying the mesh on top of the combed layer, and filling in the mesh until the groove and valley are evened out, followed by a final coat of regularising mortar. The mesh used should comply with specific characteristics for optimal performance.
Achieving optimal results with EWI-747 Lime Render and EWI-748 Lime Basecoat extends beyond the application, with the curing phase playing a pivotal role. Proper curing ensures the render achieves its intended strength, durability, and aesthetic finish.
The cornerstone of adequate curing is maintaining the correct moisture level. For EWI-748 Lime Basecoat, pre-dampening the substrate is crucial to prevent rapid drying and ensure robust adhesion and curing, mitigating the risk of cracking. Although specific details for EWI-747 Lime Render were not directly provided, similar moisture management principles apply. These principles emphasise the importance of avoiding overly quick drying, which can lead to cracking and compromised render integrity. Using a hessian sheet to manage moisture for lime-based products is crucial.
Lime-based renders are known for their gradual curing process, which is essential for their characteristic flexibility, breathability, and overall durability. The curing period can span from several days to weeks, contingent upon the render’s thickness, the prevailing environmental conditions, and the specific product characteristics used.
Cookie | Duration | Description |
---|---|---|
__stripe_mid | 1 year | This cookie is set by Stripe payment gateway. This cookie is used to enable payment on the website without storing any patment information on a server. |
__stripe_sid | 30 minutes | This cookie is set by Stripe payment gateway. This cookie is used to enable payment on the website without storing any patment information on a server. |
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
apbct_cookies_test | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_page_hits | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_prev_referer | session | Functional cookie placed by CleanTalk Spam Protect to store referring IDs and prevent unauthorized spam from being sent from the website. |
apbct_site_landing_ts | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_site_referer | 3 days | This cookie is placed by CleanTalk Spam Protect to prevent spam and to store the referrer page address which led the user to the website. |
apbct_timestamp | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_urls | 3 days | This cookie is placed by CleanTalk Spam Protect to prevent spam and to store the addresses (urls) visited on the website. |
AWSALBCORS | 7 days | This cookie is managed by Amazon Web Services and is used for load balancing. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
ct_checkjs | session | CleanTalk–Used to prevent spam on our comments and forms and acts as a complete anti-spam solution and firewall for this site. |
ct_fkp_timestamp | session | CleanTalk sets this cookie to prevent spam on the site's comments/forms, and to act as a complete anti-spam solution and firewall for the site. |
ct_pointer_data | session | CleanTalk sets this cookie to prevent spam on the site's comments/forms, and to act as a complete anti-spam solution and firewall for the site. |
ct_ps_timestamp | session | CleanTalk sets this cookie to prevent spam on the site's comments/forms, and to act as a complete anti-spam solution and firewall for the site. |
ct_sfw_pass_key | 1 month | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
ct_timezone | session | CleanTalk–Used to prevent spam on our comments and forms and acts as a complete anti-spam solution and firewall for this site. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__zlcmid | 1 year | This cookie is used by Zendesk live chat and is used to store the live chat ID. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
__utma | 2 years | This cookie is set by Google Analytics and is used to distinguish users and sessions. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmb | 30 minutes | Google Analytics sets this cookie, to determine new sessions/visits. __utmb cookie is created when the JavaScript library executes and there are no existing __utma cookies. It is updated every time data is sent to Google Analytics. |
__utmc | session | The cookie is set by Google Analytics and is deleted when the user closes the browser. It is used to enable interoperability with urchin.js, which is an older version of Google Analytics and is used in conjunction with the __utmb cookie to determine new sessions/visits. |
__utmt | 10 minutes | Google Analytics sets this cookie to inhibit request rate. |
__utmv | 2 years | The __utmv cookie is set on the user's device, to enable Google Analytics to classify the visitor. |
__utmz | 6 months | Google Analytics sets this cookie to store the traffic source or campaign by which the visitor reached the site. |
sib_cuid | 6 months | Purechat uses this cookie to send data to purechat.com, to connect visitors to the reservation team and track visitors to stay on portal. |
SRM_B | 1 year 24 days | Used by Microsoft Advertising as a unique ID for visitors. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_gtag_UA_61069204_2 | 1 minute | Set by Google to distinguish users. |
_gat_UA-61069204-2 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
ANONCHK | 10 minutes | The ANONCHK cookie, set by Bing, is used to store a user's session ID and also verify the clicks from ads on the Bing search engine. The cookie helps in reporting and personalization as well. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
NID | 6 months | NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
uuid | 6 months | MediaMath sets this cookie to avoid the same ads from being shown repeatedly and for relevant advertising. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
_clck | 1 year | No description |
_clsk | 1 day | No description |
_uetvid | 1 year 24 days | No description available. |
AnalyticsSyncHistory | 1 month | No description |
apbct_pixel_url | session | No description |
apbct_visible_fields_0 | session | No description |
apbct_visible_fields_1 | session | No description |
apbct_visible_fields_10 | session | No description |
apbct_visible_fields_2 | session | No description |
apbct_visible_fields_3 | session | No description |
apbct_visible_fields_4 | session | No description |
apbct_visible_fields_5 | session | No description |
apbct_visible_fields_6 | session | No description |
apbct_visible_fields_7 | session | No description |
apbct_visible_fields_8 | session | No description |
apbct_visible_fields_9 | session | No description |
ct_checked_emails | session | No description |
ct_has_scrolled | session | No description |
ct_mouse_moved | session | No description |
ct_screen_info | session | No description |
ictf_master | never | No description available. |
li_gc | 2 years | No description |
m | 2 years | No description available. |
SM | session | No description available. |
testinfinitycookie | session | No description |
woocommerce_show_tax | 7 days | No description available. |
wp_woocommerce_session_c5ac76b408021294cb56bcc27eddf8a1 | 2 days | No description |