{"id":7320,"date":"2026-08-06T09:44:31","date_gmt":"2026-08-06T09:44:31","guid":{"rendered":"https:\/\/checksitestatus.com\/?p=7320"},"modified":"2026-08-06T09:51:53","modified_gmt":"2026-08-06T09:51:53","slug":"site-works-on-mobile-but-not-desktop-why","status":"publish","type":"post","link":"https:\/\/checksitestatus.com\/fr\/site-works-on-mobile-but-not-desktop-why\/","title":{"rendered":"Site Works on Mobile But not Desktop &#8211; Why"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"7320\" class=\"elementor elementor-7320\" data-elementor-post-type=\"post\">\n\t\t\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-f75b11e elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"f75b11e\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-962b368\" data-id=\"962b368\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-81879e2 elementor-widget elementor-widget-text-editor\" data-id=\"81879e2\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"3:1-3:156;74-229\">You pull out your phone, load the site, and it works perfectly. You look back at your laptop, where the same URL has been failing for the last ten minutes.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"5:1-5:257;231-487\">This is a genuinely useful piece of information, even though it feels like a taunt. Your phone just told you the site is up and the server is fine. Whatever is broken lives between your desktop and the internet, and that narrows the search to a short list.<br \/><br \/><\/p><h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"7:1-7:35;489-523\"><strong>What your phone actually proved<\/strong><\/h2><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"9:1-9:73;525-597\">When the site loads on mobile data, four things got swapped out at once:<\/p><ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"11:1-14:25;599-784\"><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"11:1-11:60;599-658\">A different network, with a different route to the server<\/li><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"12:1-12:27;659-685\">A different DNS resolver<\/li><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"13:1-13:74;686-759\">A different browser, with different caches, extensions, and stored data<\/li><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"14:1-14:25;760-784\">A different IP address<\/li><\/ul><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"16:1-16:83;786-868\">One of those four is your problem. The rest of this is about narrowing down which.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"18:1-18:284;870-1153\"><strong>Note the distinction that trips people up:<\/strong> this only works if your phone is on <strong>mobile data<\/strong>, not the same Wi-Fi. If both devices are on your home network and only the phone works, you&#8217;ve eliminated the network and the culprit is almost certainly something in your desktop browser.<br \/><br \/><\/p><h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"20:1-20:55;1155-1209\"><strong>The desktop-specific causes, in order of likelihood<\/strong><\/h2><h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"22:1-22:23;1211-1233\"><strong>Browser extensions<\/strong><\/h3><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"24:1-24:61;1235-1295\">The single most common cause, and the one people check last.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"26:1-26:318;1297-1614\">Ad blockers, privacy extensions, script blockers, and corporate security add-ons all sit between your browser and the web, filtering requests. When one blocks a script the page needs to render, you don&#8217;t get a partial page. You often get nothing at all, or a blank white screen that looks exactly like a server error.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"28:1-28:154;1616-1769\">Your phone almost certainly doesn&#8217;t have those extensions installed. That asymmetry alone explains a large share of &#8220;works on mobile, not desktop&#8221; cases.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"30:1-30:168;1771-1938\">Test it: open the site in a private window, which runs without extensions by default. If it loads, disable extensions one at a time until you find the one responsible.<br \/><br \/><\/p><h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"32:1-32:19;1940-1958\"><strong>Cached content<\/strong><\/h3><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"34:1-34:253;1960-2212\">Your desktop browser has been visiting this site for months. It&#8217;s holding cached CSS, JavaScript, and possibly a cached copy of a broken version of the page from during a deploy. Your phone may have never visited at all, so it fetches everything fresh.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"36:1-36:324;2214-2537\">Service workers make this worse and are worth knowing about. A progressive web app installs a script that intercepts requests and serves content from local storage. When a service worker goes stale, it can serve a broken cached version indefinitely while the live site is perfectly fine. Hard refresh won&#8217;t always clear it.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"38:1-38:189;2539-2727\">Test it: hard refresh with Ctrl+F5 (Cmd+Shift+R on Mac). If that fails, clear site data specifically for that domain through your browser&#8217;s developer tools rather than clearing everything.<br \/><br \/><\/p><h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"40:1-40:39;2729-2767\"><strong>DNS cache and resolver differences<\/strong><\/h3><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"42:1-42:268;2769-3036\">Your desktop caches DNS lookups at the operating system level, and so does your router. If the site changed servers recently, your machine may still be holding the old IP address. Your phone on mobile data uses your carrier&#8217;s resolver, which may have already updated.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"44:1-44:123;3038-3160\">This is especially common in the day or two after a site migration, when propagation is uneven across resolvers worldwide.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"46:1-46:214;3162-3375\">Test it: flush the DNS cache. Windows: <code class=\"bg-text-200\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\">ipconfig \/flushdns<\/code>. macOS: <code class=\"bg-text-200\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\">sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder<\/code>. Then try switching to 1.1.1.1 or 8.8.8.8 to bypass your ISP&#8217;s resolver entirely.<br \/><br \/><\/p><h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"48:1-48:27;3377-3403\"><strong>Your network or router<\/strong><\/h3><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"50:1-50:225;3405-3629\">If your desktop is on Wi-Fi and the phone is on cellular, the network itself is a variable. Router DNS settings, parental controls, a firewall rule, or an ISP-level filter can each block one site while everything else works.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"52:1-52:148;3631-3778\">Office and campus networks add content filtering that blocks entire categories, sometimes returning a generic error rather than a clear block page.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"54:1-54:111;3780-3890\">Test it: tether your desktop to your phone&#8217;s hotspot. If the site loads, the fault is in your regular network.<br \/><br \/><\/p><h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"56:1-56:29;3892-3920\"><strong>VPN, proxy, or antivirus<\/strong><\/h3><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"58:1-58:151;3922-4072\">A VPN changes your apparent location and IP. Sites block VPN exit nodes routinely, and geo-restrictions may kick in based on where the exit node sits.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"60:1-60:276;4074-4349\">Security software that inspects HTTPS traffic is the sneakier version of this. Some antivirus products install a local certificate to decrypt and scan encrypted traffic, and when that mechanism breaks, HTTPS sites fail with certificate errors that look like the site&#8217;s fault.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"62:1-62:91;4351-4441\"><strong>Test it:<\/strong> disconnect the VPN. Temporarily disable HTTPS scanning in your security software.<br \/><br \/><\/p><h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"64:1-64:29;4443-4471\"><strong>Old browser, modern site<\/strong><\/h3><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"66:1-66:250;4473-4722\">Less common now, but real. If your desktop browser hasn&#8217;t been updated in a couple of years and the site uses recent JavaScript features or a modern TLS version, the page can fail to render while your regularly updated phone browser handles it fine.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"68:1-68:53;4724-4776\">Test it: update the browser, or try a different one.<br \/><br \/><\/p><h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"70:1-70:41;4778-4818\"><strong>The order to actually work through it<\/strong><\/h2><ol class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-decimal flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"72:1-77:37;4820-5178\"><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"72:1-72:88;4820-4907\">Load the site in a private window on desktop. If it works, it&#8217;s extensions or cache.<\/li><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"73:1-73:64;4908-4971\">Hard refresh. Then clear site data for that specific domain.<\/li><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"74:1-74:46;4972-5017\">Flush DNS and switch to a public resolver.<\/li><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"75:1-75:76;5018-5093\">Tether to your phone&#8217;s hotspot. If it works, the network is the problem.<\/li><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"76:1-76:48;5094-5141\">Disable VPN and HTTPS scanning in antivirus.<\/li><li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"77:1-77:37;5142-5178\">Try a different browser entirely.<br \/><br \/><\/li><\/ol><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"79:1-79:301;5180-5480\">Almost everything resolves by step three. If you get to step six and it still fails on desktop while working on mobile, you&#8217;re likely looking at something unusual: a corrupted browser profile, a hosts file entry, or DNS-over-HTTPS configured in the browser pointing at a resolver with a stale record.<br \/><br \/><\/p><h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"81:1-81:41;5482-5522\"><strong>When the problem is the site, not you<\/strong><\/h2><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"83:1-83:145;5524-5668\">Sometimes &#8220;works on mobile, not desktop&#8221; really is the site&#8217;s fault, and it&#8217;s worth knowing the shapes this takes if you&#8217;re the one who owns it.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"85:1-85:194;5670-5863\"><strong>A separate mobile site or divergent responsive breakpoints.<\/strong> If the desktop layout depends on CSS or a script that fails to load, the mobile view can render while the desktop view collapses.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"87:1-87:129;5865-5993\"><strong>Device-conditional code.<\/strong> Some sites serve different bundles by user agent. A bug in the desktop bundle affects only desktop.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"89:1-89:503;5995-6497\"><strong>Compromised sites do the reverse.<\/strong> Injected malware frequently targets mobile visitors specifically, redirecting phone users to scam pages while desktop users see a clean site. If you&#8217;re the owner and someone reports a redirect you can&#8217;t reproduce, don&#8217;t dismiss it. Content-level checks catch this where a plain availability check won&#8217;t, which is the argument for <a class=\"underline underline underline-offset-2 decoration-1 decoration-current\/40 hover:decoration-current focus:decoration-current\" href=\"https:\/\/checksitestatus.com\/website-content-monitoring-for-webpage-integrity\/\"><em><strong>monitoring page integrity rather than just uptime<\/strong><\/em><\/a>.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"91:1-91:192;6499-6690\"><strong>A CDN edge serving stale or broken assets<\/strong> to one region while other edges are fine. Your phone on a carrier network may route to a different edge node than your desktop on home broadband.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"93:1-93:412;6692-7103\">If you own the site, the useful move is checking what the server actually returns rather than what your browser displays. A 200 with a broken render is a completely different problem from a 502, and the browser&#8217;s error page hides the difference. Our <em><strong><a class=\"underline underline underline-offset-2 decoration-1 decoration-current\/40 hover:decoration-current focus:decoration-current\" href=\"https:\/\/checksitestatus.com\/http-status-codes-explained\/\">full breakdown of HTTP status codes<\/a><\/strong><\/em> covers what each response tells you about where the failure sits.<br \/><br \/><\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"95:1-95:318;7105-7422\">For anything server-side, checking the host and server response directly is faster than guessing from the front end. A <em><strong><a class=\"underline underline underline-offset-2 decoration-1 decoration-current\/40 hover:decoration-current focus:decoration-current\" href=\"https:\/\/checksitestatus.com\/check-server-check-host-website-monitoring-online\/\">server and host status check<\/a><\/strong><\/em> tells you whether the origin is healthy independent of anything happening in a browser.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-be35571 elementor-widget elementor-widget-accordion\" data-id=\"be35571\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"accordion.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"elementor-accordion\">\n\t\t\t\t\t\t\t<div class=\"elementor-accordion-item\">\n\t\t\t\t\t<div id=\"elementor-tab-title-1991\" class=\"elementor-tab-title\" data-tab=\"1\" role=\"button\" aria-controls=\"elementor-tab-content-1991\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon elementor-accordion-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-closed\"><i class=\"fas fa-plus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-opened\"><i class=\"fas fa-minus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-accordion-title\" tabindex=\"0\">Why does a website work on my phone but not my computer?<\/a>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<div id=\"elementor-tab-content-1991\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"1\" role=\"region\" aria-labelledby=\"elementor-tab-title-1991\"><p>Your phone uses a different network, DNS resolver, browser, and IP address. Any one of those can be the cause. In practice, the most frequent culprits on desktop are browser extensions blocking required scripts, cached or stale content including service workers, and a DNS cache holding an outdated IP after the site moved hosts.<\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-accordion-item\">\n\t\t\t\t\t<div id=\"elementor-tab-title-1992\" class=\"elementor-tab-title\" data-tab=\"2\" role=\"button\" aria-controls=\"elementor-tab-content-1992\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon elementor-accordion-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-closed\"><i class=\"fas fa-plus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-opened\"><i class=\"fas fa-minus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-accordion-title\" tabindex=\"0\">How do I clear DNS cache on Windows and Mac?<\/a>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<div id=\"elementor-tab-content-1992\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"2\" role=\"region\" aria-labelledby=\"elementor-tab-title-1992\"><p>On Windows, open Command Prompt and run <code class=\"bg-text-200\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\">ipconfig \/flushdns<\/code>. On macOS, run <code class=\"bg-text-200\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\">sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder<\/code> in Terminal and enter your password. Restart the browser afterwards, since browsers keep their own separate DNS cache.<\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-accordion-item\">\n\t\t\t\t\t<div id=\"elementor-tab-title-1993\" class=\"elementor-tab-title\" data-tab=\"3\" role=\"button\" aria-controls=\"elementor-tab-content-1993\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon elementor-accordion-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-closed\"><i class=\"fas fa-plus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-opened\"><i class=\"fas fa-minus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-accordion-title\" tabindex=\"0\">Can a browser extension stop a website from loading entirely?<\/a>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<div id=\"elementor-tab-content-1993\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"3\" role=\"region\" aria-labelledby=\"elementor-tab-title-1993\"><p>Yes. Ad blockers and script blockers filter network requests, and if they block something the page depends on to render, you can get a blank page rather than a partially broken one. Testing in a private window, which disables extensions by default, is the fastest way to rule this in or out.<\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-accordion-item\">\n\t\t\t\t\t<div id=\"elementor-tab-title-1994\" class=\"elementor-tab-title\" data-tab=\"4\" role=\"button\" aria-controls=\"elementor-tab-content-1994\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon elementor-accordion-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-closed\"><i class=\"fas fa-plus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-opened\"><i class=\"fas fa-minus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-accordion-title\" tabindex=\"0\">What is a service worker and why would it break my site?<\/a>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<div id=\"elementor-tab-content-1994\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"4\" role=\"region\" aria-labelledby=\"elementor-tab-title-1994\"><p>A service worker is a script that runs in the background and can intercept network requests to serve cached content, which is how progressive web apps work offline. When one becomes stale or buggy it can keep serving a broken cached version even after the live site is fixed. Clearing site data through your browser&#8217;s developer tools removes it; a normal cache clear sometimes doesn&#8217;t.<\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-accordion-item\">\n\t\t\t\t\t<div id=\"elementor-tab-title-1995\" class=\"elementor-tab-title\" data-tab=\"5\" role=\"button\" aria-controls=\"elementor-tab-content-1995\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon elementor-accordion-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-closed\"><i class=\"fas fa-plus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-opened\"><i class=\"fas fa-minus\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-accordion-title\" tabindex=\"0\">Is it the website's fault if it only breaks on desktop?<\/a>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<div id=\"elementor-tab-content-1995\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"5\" role=\"region\" aria-labelledby=\"elementor-tab-title-1995\"><p>Occasionally. Device-conditional code, a broken desktop CSS bundle, or a CDN edge serving bad assets can all produce desktop-only failures. But if other people can load the site on desktop without trouble, the cause is local to your machine. Asking a colleague to try it is a quick way to settle which it is.<\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t\t<script type=\"application\/ld+json\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Why does a website work on my phone but not my computer?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p>Your phone uses a different network, DNS resolver, browser, and IP address. Any one of those can be the cause. In practice, the most frequent culprits on desktop are browser extensions blocking required scripts, cached or stale content including service workers, and a DNS cache holding an outdated IP after the site moved hosts.<\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"How do I clear DNS cache on Windows and Mac?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p>On Windows, open Command Prompt and run <code class=\\\"bg-text-200\\\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\\\">ipconfig \\\/flushdns<\\\/code>. On macOS, run <code class=\\\"bg-text-200\\\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\\\">sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder<\\\/code> in Terminal and enter your password. Restart the browser afterwards, since browsers keep their own separate DNS cache.<\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Can a browser extension stop a website from loading entirely?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p>Yes. Ad blockers and script blockers filter network requests, and if they block something the page depends on to render, you can get a blank page rather than a partially broken one. Testing in a private window, which disables extensions by default, is the fastest way to rule this in or out.<\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"What is a service worker and why would it break my site?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p>A service worker is a script that runs in the background and can intercept network requests to serve cached content, which is how progressive web apps work offline. When one becomes stale or buggy it can keep serving a broken cached version even after the live site is fixed. Clearing site data through your browser&#8217;s developer tools removes it; a normal cache clear sometimes doesn&#8217;t.<\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Is it the website's fault if it only breaks on desktop?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p>Occasionally. Device-conditional code, a broken desktop CSS bundle, or a CDN edge serving bad assets can all produce desktop-only failures. But if other people can load the site on desktop without trouble, the cause is local to your machine. Asking a colleague to try it is a quick way to settle which it is.<\\\/p>\"}}]}<\/script>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-4a2892f elementor-widget elementor-widget-text-editor\" data-id=\"4a2892f\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"114:1-114:21;9332-9352\"><strong>The short version<\/strong><\/h2><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"116:1-116:143;9354-9496\">Your phone working is good news. It means the server is up and the fix is on your side, which is the side you can actually do something about.<\/p><p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"118:1-118:101;9498-9598\">Private window, hard refresh, flush DNS. Three steps, about a minute, and that&#8217;s most cases handled.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>You pull out your phone, load the site, and it works perfectly. You look back at your laptop, where the same URL has been failing for the last ten minutes. This is a genuinely useful piece of information, even though it feels like a taunt. Your phone just told you the site is up and [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":7321,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22],"tags":[471,472,477,476,474,473,469,475,478,470],"class_list":["post-7320","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-website","tag-browser-extension-blocking-site","tag-clear-dns-cache","tag-desktop-browser-troubleshooting","tag-https-scanning-antivirus","tag-private-browsing-test","tag-service-worker-cache-issue","tag-site-works-on-mobile-not-desktop","tag-vpn-blocking-website","tag-website-loading-problems","tag-website-not-loading-on-computer"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/posts\/7320","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/comments?post=7320"}],"version-history":[{"count":4,"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/posts\/7320\/revisions"}],"predecessor-version":[{"id":7325,"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/posts\/7320\/revisions\/7325"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/media\/7321"}],"wp:attachment":[{"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/media?parent=7320"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/categories?post=7320"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/checksitestatus.com\/fr\/wp-json\/wp\/v2\/tags?post=7320"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}