Rendering the façade of your property is not entirely straightforward. As such, many problems can occur. These problems are either functional or visual, but all have their solutions and ways to prevent them. Whilst functional problems are naturally worrying, visual problems can leave you feeling disheartened. The process of refreshing your façade is not altogether cheap. Therefore if the finish is not what you envisioned, there will be issues. In today’s blog, we examine the different types of visual problems and how to fix them.
Efflorescence is when water seeps through the wall and dissolves minerals. As the water evaporates from the surface of the render, these minerals are left behind and form a white, powdery residue. Depending on the severity, efflorescence can be a cosmetic issue or indicate potential structural problems, like a faulty damp-proof course or high groundwater levels.
Efflorescence can often be removed by mechanically cleaning the surface using a stiff brush or pressure washing. However, it’s important to identify and address the source of water infiltration to prevent its recurrence. This may involve repairing cracks, improving drainage, or addressing other issues causing moisture penetration.
Typically, these thrive in damp and shaded conditions. Mould might appear as black or dark green splotches, while algae often have a green or red appearance. Besides being unsightly, if left untreated, mould can lead to health problems for residents and cause the render to fail over time.
Treating mould and algae typically involves cleaning the affected areas with a mildewcide or fungicide, followed by proper ventilation and moisture control. In some cases, it may be necessary to remove and replace the affected render if the infestation is severe.
Fine hairline cracks can occur due to natural shrinkage as the render dries. However, larger cracks often indicate more serious issues. Problems such as structural movement, incorrect render mix (too much cement, for example, can make the render too rigid and therefore prone to cracking), or poor application techniques can be expensive to fix.
Small hairline cracks can be repaired using flexible sealants or patching compounds specifically designed for exterior use. Larger cracks may require more extensive remediation, such as cutting out and replacing the damaged render or addressing underlying structural issues.
Render peels or flakes off if the original substrate is not properly prepared, if the wrong type or amount of bonding agent is used, or if the render dried too quickly (often due to applying in direct sunlight or high wind conditions). Render can also peel or flake due to a poor mechanical key.
To fix the peeling or flaking render, the loose or damaged areas need to be removed, and the surface should be properly prepared. This may involve repairing the substrate, applying suitable bonding agents, and reapplying a fresh layer of the render using proper techniques.
This refers to visible streaks or patches that appear on the surface of the render. It’s typically caused by moisture, often condensation, which allows for the migration of substances from the substrate or within the render itself. This can leave visible outlines of the underlying structure’s features.
Ghosting is often difficult to eliminate completely, but improving ventilation and addressing moisture issues can help reduce its appearance. Regular cleaning and maintenance of the render surface may also help minimise the visibility of ghosting.
Damp patches can appear if the render allows water to penetrate. This could be due to cracks, poor-quality render, or issues with the building such as leaking gutters or pipes. Dampness can lead to more serious problems like mould, structural damage, and internal water damage. There are different forms of moisture, including penetrating and rising dampness.
Identifying and addressing the source of moisture infiltration is crucial to resolving dampness issues. This may involve repairing leaks, improving drainage systems, applying waterproof coatings, or installing additional moisture barriers.
If moisture gets trapped under the surface of the render, it can cause the render to lift away from the wall, forming bubbles or blisters. This is typically due to poor application technique, allowing water to get behind the render — evaporation forces the embedded moisture out of the wall.
Bubbles or blisters in the render may indicate trapped moisture. The affected areas should be carefully inspected, and if necessary, the render may need to be removed, and the underlying substrate repaired or replaced before reapplication of render.
Dirt and pollution can cause staining over time, as can certain vegetation types. Rust stains can occur due to metal fixtures on the façade. Moreover, black stains can occur due to pollution or mould. Render staining often occurs around the building’s plinth. The type of staining will tend to be dirt splashback and manifests in the render looking yellowed. Specially designed renders like Mosaic Render combat this staining.
Stains can often be removed through cleaning techniques such as pressure washing or using appropriate cleaning agents. If the staining is persistent, it may be necessary to consider stain-resistant coatings or surface treatments.
UV radiation can cause the colour pigments in the render to break down over time, causing it to fade. Some colours are more prone to this than others, especially deeper, more vibrant colours. However, specially designed silicone renders have resistance to UV radiation. Therefore, their colour does not fade.
Fading cannot be reversed, but it can be addressed by repainting or applying a fresh coat of render with UV-resistant pigments. Choosing fade-resistant render materials and pigments can also help prevent future fading.
If the render hasn’t appropriately bonded to the underlying wall or there is structural movement, areas of the render can detach from the substrate. This is a serious issue as large render pieces can potentially fall off, posing a safety risk.
Addressing render detachment involves identifying the underlying causes, such as poor bonding or structural issues, and implementing appropriate remedial measures. This may include removing and reapplying the affected render, reinforcing the substrate, or addressing any structural movement.
Let us know below if you’ve encountered any of these issues and if we can help!
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 |
4 thoughts on “How to Fix Visual Problems with Your Façade”
We’ve had our property rendered for 2 years and we’ve recently had a large portion of a wall damaged – What do you recommend for fixing this?
Hi Jenny, how extensive is the damage? If it is just surface render damage, you can patch this up. However, if the damage is more extensive, we’d recommend removing a considerable portion of the area and re-rendering, ideally with our Silicone Render which is extremely durable.
The damage is what I would consider ‘surface’ damage, a small dent and a few cracks. How would you recommend we fix this with a patch?
We’d always recommend contacting your installer, you could be covered by a warranty. They’ll remove the area, re-apply basecoat and mesh if required, and re-render to match the surrounding wall.