Slow Roads Unblocked: Playing on a School or Work Network
"Blocked" is three different problems wearing the same coat
When someone says Slow Roads is blocked at school, they usually mean one of three unrelated things, and the fix for each is completely different. Two of them have nothing to do with your network administrator at all. Before you try anything, work out which one you actually have, because the symptoms are easy to tell apart once you know what to look for.
| You never reach the site | Domain or category filtering. A block page appears, or the tab errors out instantly. |
|---|---|
| The site loads, the game crawls | Hardware acceleration is off. You get a playable but unusable 3-8 frames per second. |
| The loading bar stops | Either the assets are still crawling in over a saturated network, or world generation has stalled. The game gives up on the second of those after three seconds. |
| Totally blank page | Site data is blocked for the origin. Rare, but it kills the app before it draws anything. |
This page takes each in turn and is honest about which are fixable from your side. For the general performance write-up rather than the managed-device version, the lag and frame rate guide goes deeper on settings.
Cause 1: the domain is filtered
The signature is that you never see the game at all. Either a branded block page appears with your school or company logo and a category name like Games, or the request dies immediately with a DNS error rather than a timeout. The giveaway is speed. Filtering happens before anything is downloaded, so the failure is instant. A real network problem takes several seconds to fail.
Some filters work from a list of specific domains; others use a category assigned to every domain by a classification service. That distinction is the whole reason a mirror sometimes loads when slowroads.io does not: a list-based filter has an entry for the well-known domain and nothing for a smaller one. A category-based filter classifies the mirror the same way sooner or later and blocks it too. Neither outcome is something this site controls.
If your network deliberately blocks games, that is a policy decision made by whoever runs the network, and getting around it is not something this guide covers. Proxies, VPNs and extension tricks are outside scope. Ask, or play at home.
Cause 2: hardware acceleration is disabled
This is the one that catches most people, and it is not a network problem at all. The page loads perfectly. The splash screen appears. You click begin, and the game runs like a flipbook. Managed Windows machines and managed Chromebooks very often ship with GPU acceleration turned off by device policy, which forces the browser to render 3D through a software rasteriser on the CPU. Slow Roads is built on three.js and redraws the entire visible landscape every frame, so software rendering does not give you a slower game. It gives you a slideshow.
The game diagnoses this for you
There is a detector in this build that most players never notice. The renderer counts frames and averages them over five-second windows. Once more than three of those windows have gone by, if the average is below 45 frames per second, a panel appears reading Low FPS? Try lowering the quality settings or enabling hardware acceleration, with an arrow pointing down at the settings. It fires once and then permanently disables itself, writing a flag to storage so it will not reappear on later visits either.
Two things suppress it before it can ever fire, both worth knowing if you are wondering why the game never warned you. It is switched off from the start if view distance or environment detail is already set to low, on the reasoning that you have clearly found the settings already; and it is switched off if you have changed a quality setting at any point in the past. So a machine that has been tuned down once will never nag you again, however badly it is running.
If that prompt showed up around twenty seconds into your first drive, the game has already told you what is wrong. The FAQ inside the same bundle gives the same answer to the question "Why does it run so poorly/like a slideshow?" — check that the browser is running with hardware acceleration enabled, in both the browser settings and the GPU settings.
Confirming it in thirty seconds
Open chrome://gpu in a new tab. The list at the top shows each graphics feature and how it is being run. Look for the WebGL and WebGL2 rows. Hardware accelerated is what you want. Software only, hardware acceleration unavailable or Disabled confirms the diagnosis. Further down, the Graphics Feature Status section normally states the reason, and on a managed device it will say the feature was disabled by policy or by a command line flag.
On a personal machine, chrome://settings/system holds the "Use graphics acceleration when available" toggle. Turn it on and restart the browser completely, not just the tab. On a managed machine that toggle is greyed out with an enterprise policy badge beside it, and clicking will not move it. What remains is making the game cheap enough that a weak integrated GPU, or even a software rasteriser, can keep up — the Chromebook section below.
MDN's WebGL API documentation explains what the browser is being asked to do here, and why losing the GPU is so catastrophic for it.
Cause 3: the first load never finishes
Two different things hide behind a stuck loading bar, and it is worth separating them, because only one of them is the network's fault.
The assets are still arriving
School and office networks are shared, and at nine in the morning they are saturated. A first visit has to pull down two JavaScript chunks of roughly 1.1 MB each, plus the audio and textures the scene needs — around 16 MB in total across about 180 files. On a throttled connection that takes a while, and until the bundles have executed there is no loading bar at all: you get a blank tab that eventually becomes the splash screen. If the tab sits empty for thirty seconds and then works, this was it, and the second visit will be quick because the browser caches the lot.
Generation has stalled
Once the bundles are running, the bar you are watching is not a download bar. It tracks the game building the world: the terrain heightmap, the scene, the road midline, the far grid. Each stage reports fine-grained progress every frame, and the loader keeps a running inactivity timer. If that progress figure fails to advance for more than three consecutive seconds, the loader concludes the generation has wedged and stops.
What happens next depends on whether the browser has seen this game before. A returning player gets a screen titled Critical Error, reading "Apologies - please click below to continue with a different generation seed. Your distance progress will carry over," with a reload button beneath it. A first-time visitor gets a silent retry on a fresh seed and never sees the error at all — which is why someone sitting next to you, on the same network and the same model of laptop, can appear to have no trouble while you are staring at an error screen.
That error screen also claims "This error has been recorded for investigation." On this site it is not. The telemetry socket in the original build pointed at a server that no longer answers, and this build sets analytics-disabled before the game boots. Nothing is sent anywhere. The sentence is simply text left over in the 2022 bundle.
Press the game's own reload button rather than reloading the tab. It picks a new seed, which is the actual fix, where a tab reload would hand the generator the same seed and often the same wedge. If you keep landing on it, change the seed yourself in the menu — a stalled generation is a property of one particular arrangement of hills, not of your machine.
The rare one: a blank page with no splash
If you get a completely blank or black page with no logo and no loading bar, and the browser console shows a SecurityError, the cause is site data being blocked for the origin. The bundle reads localStorage at module scope, before React mounts, and that read is not wrapped in a try/catch. If the browser refuses the access, the module throws and nothing renders at all.
Allowing site data for the origin fixes it. Some managed profiles block storage globally, in which case this build cannot run on that profile at all — a limitation of the 2022 code rather than something a mirror can patch around. It would also have cost you everything that persists: the seed, every quality setting and your distance records all live in localStorage.
Chromebooks
Most people searching for an unblocked version are on a school Chromebook, so it is worth being specific. Two things are true of almost all of them.
Input is never the problem. Chromebooks have real keyboards, and this build reads physical key positions through e.code rather than the character produced. That is the same mechanism behind the 1.0.1 changelog line about AZERTY support: WASD sits where ZQSD is on a French layout, and it just works. The search key where caps lock usually is, the missing function row and the Chromebook's remapped top row do not touch anything the game binds. W accelerates, S brakes and then reverses, A and D steer, Space is the handbrake, C cycles the three cameras, R resets the vehicle to the road and F hands over to autodrive. The full controls guide has the rest of the table.
The GPU is always the problem. The integrated Intel UHD, MediaTek and ARM chips in education-model Chromebooks can run this at a steady frame rate, but not at default quality on a 1080p panel. The fix is mostly one setting.
Settings that work on weak managed hardware
| Render scale | 0.5. The single biggest win. The options are 0.5, 0.75, 1 and 1.5; halving it quarters the number of pixels the GPU has to shade. |
|---|---|
| View distance | low. Second biggest win, because it cuts how much terrain is generated and drawn each frame. |
| Environment detail | low, or med once render scale is down. This controls scenery density. |
| Antialias | off. A smaller effect than the three above, but free. |
| Scene | Hills. The off-world scenes are not meaningfully cheaper, and Hills is the one with all four seasons. |
| Road complexity | easy. Worth understanding properly: easy is a wider road, 3.2 against normal's 3, built from fewer noise octaves. Bigger, smoother landforms rather than gentler ones, and less detail to generate. |
Change render scale first and judge from there. A Chromebook that was unplayable at defaults often sits comfortably above 45 frames per second with nothing else touched. There is no shadow quality setting in this build, so do not go looking for one — shadow resolution rides along with environment detail and has no control of its own.
What will not work on a Chromebook
Tablet mode and touchscreen models get no benefit, because this build has no touch controls of any kind. Detach the keyboard and you get a notice saying the project is not yet supported on mobile devices as it requires a hardware keyboard. An override button writes force-allow-mobile to storage and reloads, but it only lets you past the notice — it does not add a single on-screen control. The mobile guide covers that in full.
What you are actually playing here
What you are driving here is the public web build of Slow Roads as it stood in late 2022, version 1.0.1, made by anslo. It is a genuine capture of that build rather than a reimplementation, which is why the behaviour described above can be quoted exactly rather than guessed at.
The official game has kept developing since then and has things this snapshot does not. If the domain is reachable for you, slowroads.io is the one to play and the one to support. This copy is for when it is not reachable, and for people who specifically want the 2022 version. More on that on the about page.
If your diagnosis landed on cause 2 or cause 3, the sensible next step is to start a drive and work through the quality settings while you are in it. Twenty seconds of driving is enough for the game to tell you whether it is happy.
Play Slow Roads → Free in your browser. Desktop or laptop with a keyboard.