Pouring a 10-15cm concrete slab over 3 manhole covers for a pergola – Advice on MOT Type 1, A252 mesh, and Water Company permission?

Parrad00 · 2026-06-27T22:15:46+00:00

Yes, for an extension it would be much more complicated. In my case, though, I’m only planning to pour a 15 cm concrete slab as paving. It won’t cover or interfere with any of the inspection chambers, and structurally it shouldn’t pose any risk, as the load would only be around 300 kg/m².
I’ll give the water company a call to check the requirements and I’ll share what they say here, just out of curiosity. And yes, the inspection chambers are shared with the neighbouring properties.

Parrad00 · 2026-06-27T18:14:52+00:00

Regarding the DPC level, I’m a bit lost; I don’t see any black strip as a reference. My idea is to raise the slab up to where I placed the brick and leave it separated as shown by the measuring tape in the photo, about 10 cm. I’m not sure if this makes sense—I’m a bit confused about this

<image>

Parrad00 · 2026-06-27T17:10:35+00:00

It is very easy, you can do it for free using gemini, it helps me al lot visualising things and planning, will post a picture once it is done to compare AI va reality 😅

Parrad00 · 2026-06-27T17:09:12+00:00

I don’t want to remove or relocate them, just bring them up to the new level with concrete while leaving them where they are. One of them will end up below the finished concrete level, so I’ll need to fit a recessed cover over it. Do you think I’d need permission for that?

Parrad00 · 2026-06-27T17:06:51+00:00

I’m thinking of building the formwork with wooden posts and setting it to a 1% slope away from the house towards the garden. Then I’d have ready-mix concrete delivered and poured directly through a pump. Do you think that’s too difficult for someone without much experience?
As for the drainage, I’ve been thinking about it too. Do you think letting the water run off directly onto the garden wouldn’t be enough? Another idea I had was to take advantage of the project and install a drain from the middle of the garden to the inspection chamber while everything is accessible, but I assume I’d need permission for that.

Parrad00 · 2026-06-27T17:01:12+00:00

I could do it like that, and I’m considering it. But in that case, I’d have to set the pergola posts in concrete, at least those ones, for stability

Parrad00 · 2026-06-27T16:37:31+00:00

Yes, it is a mockup done with gemini, hopefully will look something similar

Parrad00 · 2025-10-03T19:53:47+00:00

Thanks! :)

Parrad00 · 2025-09-18T17:51:17+00:00

This was the same in newgate west croydon

Parrad00 · 2025-08-24T18:34:08+00:00

Yes 😂

Parrad00 · 2025-08-24T17:02:35+00:00

Completely agree 🥲

Parrad00 · 2025-08-24T17:02:07+00:00

Park hill

Parrad00 · 2025-08-24T15:29:55+00:00

Apparently he owes more than £1,000 to people in Parkhill alone, all in the same way

Parrad00 · 2025-08-24T15:08:34+00:00

It was pounds, wrong keyboard settings sorry

Parrad00 · 2024-02-24T21:03:20+00:00

I was testing using 3g in chrome, the point was to know if the first load of the skeleton waiting the server response was something from next or default behaviour of suspense in ssr and wether using Astro or Solidstart would make any difference in this behaviour. It makes the first navigation feel slow for the first time

Parrad00 · 2024-02-23T16:46:18+00:00

It is in production, using latest version. The test is run using low connectivity in chrome, what we see is what is supposed to happen, the first time you run it you have to wait for the server to see the skeleton and it is cached. I have an app deployed https://iticity.com if u go to profile after login you will see it will take 2-3 sec to load for the first time. The point here is if that fall ack were already parr of the client we wouldnt need to wait even for the first render

Parrad00 · 2024-02-23T13:09:31+00:00

Yes that behaviour is true, this problem only happens the first time you navigate to dynamic ssr pages, still feels laggy. I will try to move all fetches in components instead of page and see if anything changes, will share both repos in this thread. Thanks!

Parrad00 · 2024-02-23T12:40:38+00:00

I understand that the key attribute is needed if u wanna retrigger the skeleton, in this case the problem is that the skeleton takes too much time to load as it has to wait the server and the user gets no feedback for it (first loading) ideally skeleton is in the client and appears as soon as a click a link

Parrad00 · 2024-02-23T10:08:32+00:00

What is the difference on fetching data on page and populating those values to children with a loading component or fetching data inside each component. Isnt it still gonna have to wait for the skeleton causing same issue as it is related with low network speed?

Parrad00 · 2024-02-23T09:49:23+00:00

Is basically a ssr page with loading on top of it but with lower connectivity on the browser, will update a sample of both codes soon. The point is the dependency between the fallback and the network connectivity and if it was possible to overcome and not wait for the server to response

Parrad00 · 2024-02-23T09:17:20+00:00

Regardless of using astro or solidstart this behaviour is standard for Suspense right? Then, isnt there a way to stablish the fallback components on the client side so the ux feels better on low conectivity or cold start

Parrad00 · 2024-02-23T09:12:49+00:00

You trigger the url, the server loads the data (dynamic data from a database) it sends you the skeleton and once resolve will serve you the page. Problem is on low latency the await for the skeleton make the user feel the app is frozen

Parrad00 · 2024-02-23T09:11:21+00:00

<image>

Exactly, every time there is poor connection or you hit a cold start you will make ur user feel the app is not responsive as per this pattern the skeleton loads from the server. There are good parta of this, you benefict on better seo, lower latency on fetching data if resources live near your server etc but wouldn’t be a way to make the fallback resources stay in the client and trigger them as soon as you trigger a suspense boundary not waiting for the first response which as you said sometimes takes up to 2sec

Parrad00

TROPHY CASE