# Website analysis: how to check your own site in ten minutes | Fokuus [Home](https://fokuus.be/en/) [Blog](https://fokuus.be/en/blog/) Website analysis: how to check your own site in ten minutes # Website analysis: how to check your own site in ten minutes Website analysis without a paid tool: six checks in ten minutes with PageSpeed Insights, Search Console and your own phone. With what each score does and doesn't say. [Anton Pycarelle](https://fokuus.be/en/about/) 25 September 20268 min read time ## In this article - [1. Measure speed in PageSpeed Insights](https://fokuus.be/#1-snelheid-meten-in-pagespeed-insights) - [2. Check in Search Console whether Google knows your pages](https://fokuus.be/#2-in-search-console-nakijken-of-google-je-pagina-s-kent) - [3. Your title as Google displays it](https://fokuus.be/#3-je-titel-zoals-google-hem-toont) - [4. One address, via HTTPS](https://fokuus.be/#4-een-adres-via-https) - [5. Your site on your own phone](https://fokuus.be/#5-je-site-op-je-eigen-gsm) - [6. Test your form and count what comes in](https://fokuus.be/#6-je-formulier-testen-en-tellen-wat-er-binnenkomt) - [So you know if your round was successful](https://fokuus.be/#zo-weet-je-of-je-rondje-geslaagd-is) A free website analysis gives you a score on 100 quickly, with some red, orange and green. What you rarely get with it: which score matters, which you can ignore, and whether a request through your site actually comes in. That last one weighs most heavily for an SME, and no scan can test it: it doesn't look in your mailbox. A website analysis for an SME comes down to four questions: does your site load smoothly on a phone, does Google know your pages, does your search result look good, and do requests come in? Below is a ten-minute round that answers that, with free Google tools and your own phone. Where possible, I use our own site as an example, even where it doesn't score well. Six checks, together ten minutes. The last one weighs most heavily, and no scan tool looks in your mailbox. ## 1. Measure speed in PageSpeed Insights Go to [pagespeed.web.dev](https://pagespeed.web.dev/) , paste your homepage address and click Analyze. Choose the Mobile tab, because that's where we see the difference: on 25 September 2026 fokuus.be scored 99 to 100 for performance on desktop, 73 to 74 on mobile. The report has two sections. At the top are measurements from real Chrome visitors over the past 28 days, below that a simulation: for mobile a mid-range device on a mobile network (in our report a Moto G Power on slow 4G), for desktop a computer with a wired connection ([Google's explanation](https://developers.google.com/speed/docs/insights/v5/about) ). For fokuus.be it says at the top "No data": Google only shows those figures when enough real visitors have been measured. One of our measurements on 25 September 2026 on mobile: no real user data, 74 for performance and a red LCP of 4.8 seconds. In the circles, 90 to 100 is good, 50 to 89 is fair and below 50 is poor. Below that, first look at Largest Contentful Paint (LCP), the time until the largest piece of content is in view. For real visitors, Google calls 2.5 seconds or less good, up to 4 seconds needs improvement and above that is poor; for simulation that's a guideline. For Cumulative Layout Shift (CLS), how much your page shifts, 0.1 or less is good ([web.dev](https://web.dev/articles/vitals) ). Interaction to Next Paint (good: 200 milliseconds or less) cannot be measured by a simulation because no one clicks. Total Blocking Time serves as a replacement. Our mobile LCP fluctuated that day between 4.7 and 4.8 seconds, so red; CLS and Total Blocking Time were at 0, green. The largest element is the device mock-up at the top of our homepage, and according to the report most of the time doesn't go to downloading that image, but to waiting for it to display. A red mark on our own site, but the report shows which phase loses time, and that tells you more than a single score. Where measuring goes wrong: the score varies from measurement to measurement, as you can see from our own figures. So measure at least twice, and compare after an adjustment under the same conditions. Also click open what's wrong under a score: our SEO score is 92 because of one line in our robots.txt file, a directive for AI systems. Lighthouse, the engine behind PageSpeed, doesn't recognize that rule. Google only supports user-agent, allow, disallow and sitemap in robots.txt, and [ignores invalid rules](https://developers.google.com/crawling/docs/robots-txt/robots-txt-spec) . A 92 from a deliberate rule is different from a 92 from a forgotten block. Conversely, 100 is no guarantee. Why that particularly holds for accessibility, read [our post about the European Accessibility Act](https://fokuus.be/en/blog/european-accessibility-act-website/) . ## 2. Check in Search Console whether Google knows your pages Whether Google indexes your pages, you can see in Google Search Console, free after a one-time verification of your site. Type the full address of a page in the search bar at the top, that's the [URL inspection](https://support.google.com/webmasters/answer/9012289?hl=nl) . Do it for your homepage and your main service page. Our homepage was on 25 September 2026 on "Submitted and indexed". If the URL is indexed, the page can appear in Google, though a place in search results is not guaranteed. If you see "Crawled - currently not indexed", Google visited the page but didn't index it, and [according to Google](https://support.google.com/webmasters/answer/7440203?hl=nl) that can still happen later, but it's not certain. For a page a few days old, that's not a red flag: our new blog posts get indexed within about two weeks. If an important page stays there for months, it usually says something about the content. We learned that the hard way with 29 of our 32 old blog posts, which never got indexed; what we did about it is in [our SEO tips](https://fokuus.be/en/blog/seo-tips/) . No Search Console? Then type in Google `site:jouwdomein.be`, but don't count the results: according to Google, that search query doesn't necessarily show [all indexed pages](https://developers.google.com/search/docs/monitor-debug/search-operators/all-search-site) . For fokuus.be Google estimated around 200 results with a sitemap of 96 addresses. What that search query is good for: seeing if there are pages in the index you didn't expect. ## 3. Your title as Google displays it Search for your business name and read the blue title. Google creates that title automatically and doesn't always use the title you set: headings and link text can also serve ([Google on titles](https://developers.google.com/search/docs/appearance/title-link) ). In our code it says "Websites, online stores and automation | Fokuus". Google showed on 25 September 2026 "Fokuus: Websites, online stores and automation". Perfect: the name up front, the message intact. Red flags are a vague title like "Home", the same title on every page, or a title that gets cut off before the word you want to be found for. Google shortens titles to screen width, so check on your phone too. ## 4. One address, via HTTPS Type your domain in the address bar, once with www in front and once without. Both should end up at the same address: with us www.fokuus.be redirects to fokuus.be. It's better not to test the HTTP side in your browser. Chrome automatically converts an HTTP address to HTTPS if your site can handle it ([Chromium blog](https://blog.chromium.org/2023/08/towards-https-by-default.html) ), so what you see doesn't prove your server forwards it. Look for that in the [HTTPS report](https://support.google.com/webmasters/answer/11396518?hl=nl) from Search Console. It shows how many indexed pages are on HTTP and HTTPS; ideally none on HTTP. Red flag: HTTP pages in that report, or a version with and without www that both load. ## 5. Your site on your own phone Google used to have a separate mobile-friendly test, but it was [discontinued on 1 December 2023](https://developers.google.com/search/blog/2016/05/a-new-mobile-friendly-testing-tool) . Test it yourself then. Turn off your wifi, open your homepage and tap your phone number: does your phone app open? Open the menu, read a paragraph without zooming, and scroll to the bottom. Red flag: zooming needed, buttons so close together you misclick, or a notification that covers your call button. And your own phone is probably faster than your customer's: if your site feels smooth to you, that red LCP from step 1 could still be right. ## 6. Test your form and count what comes in Fill in your own contact form, once on your phone and once on your computer, with an email address different from your business email. Check if the email arrives, including in spam, and whether the visitor sees a confirmation after sending. If you don't immediately know which address those emails go to, that's already a finding. Then count what came in through the form over the past three months, and separate real requests from tests and spam. When we checked that for fokuus.be on 16 September 2026, our own form had not generated any real requests, only tests and spam. A form that works technically can still yield nothing, and our own AI check doesn't test that either. How to get usable requests from it, you can read about [improving your contact form](https://fokuus.be/en/blog/contact-formulier-meer-leads/) . ## So you know if your round was successful After ten minutes you don't have a score, but six answers. Note them with the date: that list is your baseline. If you change something, repeat the same step the same way. In URL inspection, you can use "Test live URL" to check the current version of a page, after which you can request indexing. The figures for real users in PageSpeed are over 28 days; you'll see an improvement from today only gradually there. Prefer not to do it yourself? Our free [AI check](https://fokuus.be/en/ai-check/) does part of this work automatically, from its own angle: can search engines and AI assistants such as ChatGPT technically reach and read your website? Among other things, it checks your robots.txt, sitemap, titles, HTTPS, mobile display and speed. Your score appears after the scan, without an account; you receive the full report through a link by email. Step 6 remains manual work even then. Website analysis PageSpeed Insights Search Console Core Web Vitals Share [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Ffokuus.be%2Fen%2Fblog%2Fwebsite-analyse%2F) [DotsApp](https://wa.me/?text=Website%20analyse%3A%20zo%20check%20je%20je%20eigen%20site%20in%20tien%20minuten%20https%3A%2F%2Ffokuus.be%2Fblog%2Fwebsite-analyse%2F) [Email](mailto:?subject=Website%20analyse%3A%20zo%20check%20je%20je%20eigen%20site%20in%20tien%20minuten&body=https%3A%2F%2Ffokuus.be%2Fblog%2Fwebsite-analyse%2F) ## Get Fokuus updates. New articles and Fokuus's updates in your mailbox. You can unsubscribe at any time. ## Anton Pycarelle Founder of Fokuus Anton builds and optimizes websites for Belgian SMEs from Kortrijk. He writes about choices and experiences from real projects. [More about Fokuus](https://fokuus.be/en/about/) ## Keep reading. [All articles](https://fokuus.be/en/blog/) Maintenance & Technique · 7 min reading time ### What is hosting? How to find out where your website lives What is hosting, how is it different from your domain name, and what does it cost? With a step-by-step plan to find out where your website is and who has access to it. [Maintenance & Technique · 7 min reading timeWhat is hosting? How to find out where your website livesWhat is hosting, how is it different from your domain name, and what does it cost? With a step-by-step plan to find out where your website is and who has access to it.](https://fokuus.be/en/blog/wat-is-hosting/) Maintenance & Technique · 7 min reading time ### European Accessibility Act in Belgium: What Must Your Webshop Do? Since 28 June 2025, Belgian webshops for consumers must be accessible; microenterprises only from 2030. Who is covered, and what actually helps? [Maintenance & Technique · 7 min reading timeEuropean Accessibility Act in Belgium: What Must Your Webshop Do?Since 28 June 2025, Belgian webshops for consumers must be accessible; microenterprises only from 2030. Who is covered, and what actually helps?](https://fokuus.be/en/blog/european-accessibility-act-website/) [Bron](https://fokuus.be/en/blog/website-analyse/) · [Agentdocumentatie](https://fokuus.be/developers/)