Cleveland by Jay

Author: Jay

  • By the numbers…PageSpeedInsights

    By the numbers…PageSpeedInsights

    Google Site Kit

    After some observing, there is a panel where we find out how visitors experience our site. Our scorecard is poor

    Look below

    ..moving on to recommendations on how to improve:

    Reduce unused CSS

    Consider reducing, or switching, the number of WordPress plugins loading unused CSS in your page. To identify plugins that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a stylesheet if it is actually used on the page.

    Reduce unused JavaScript

    Consider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your page. To identify plugins that are adding extraneous JS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the script. Look out for plugins that have many scripts in the list which have a lot of red in code coverage. A plugin should only enqueue a script if it is actually used on the page.

    and finally

    Avoid enormous network payloads

    Consider showing excerpts in your post lists (e.g. via the more tag), reducing the number of posts shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.

    And here we ca run the pagespeedinsights

    https://pagespeed.web.dev/analysis/https-staywithjay-com/coksxvdd0v?utm_source=sitekit&form_factor=mobile

    and really gives a report on that page.. I like that

     

    Bottom linee quite a bit of work to be done on this topic.

    What is the difference between the home page performance and other pages?

    https://pagespeed.web.dev/analysis/https-staywithjay-com-checkin/g3bayk9684?form_factor=mobile

     

    A little better than the home page..

     

    This is called a lighthouse Treemap. I had never seen this…

     

    Why are we working on this?

    We believe there is a relationship between how our website performs (espcially the mobile one) and how many of our guests convert from First Time into Many Times guests.

     

    The first step our platform already does, and fairly well.

    Collects information of every single guests that comes ffrom the OTA,

    including their interests and reasons for travelling when possible.

     

    As we move to more and more guests booking through our preferred method direct (hospitable connector) we need to. make sure when guests land on those pages they can easily complete their booking and get all relevant informaitoon.

    We ran the same #pageSpeedInsights for the #hosptaible site our book.staywithjay.com and to our surprise it has a poorer performance then the page we designed in house.

     

    https://pagespeed.web.dev/analysis/https-book-staywithjay-com/5lgmsoft2n?form_factor=mobile

     

  • Click for Lost and Found Code

    Click for Lost and Found Code

    050326

    plus pound sign.

     

    Driveway Entrance.

  • Lost & Found – Process & Policy

    Lost & Found – Process & Policy

    Lost & Found – Process & Policy

    How It Works

    1. Item Reported or Identified
      An item is either:

      • Reported lost by the guest, or
      • Identified and logged by our team during turnover.
    2. Item Confirmation
      Once the item is located and verified, the guest will be notified.
    3. Recovery Scheduling Required
      To retrieve the item, the guest must:

      • Use the “Recover My Lost Item” link
      • Select an available pickup time between 10:00 AM – 7:00 PM
      • Pay a $15 recovery and handling fee
    4. Access Instructions Issued
      After confirmation:

      • The guest receives a one-time access code or instructions via the confirmation page
    5. Item Pickup
      • Pickup must occur at the scheduled time
      • Access is limited strictly to the retrieval process

    Rules & Enforcement

    • One Scheduled Opportunity Only
      Each item is assigned one pickup window.
    • Missed Pickup = Item Abandoned
      If the scheduled pickup is missed, the item is considered abandoned and discarded.
    • No Re-Entry or Unscheduled Access
      • No drop-ins
      • No early/late arrivals
      • No “quick pickups” outside the system
    • No Storage Service
      We are not a storage facility. All recovery must follow the process.
    • Handling Fee Applies to All Recoveries
      The $15 fee covers coordination, handling, and access management.

    This structure aligns with our broader operational model—clear expectations, controlled access, and no exceptions, which is consistent with how other rules are enforced across SWJ properties.

  • O zelador

    O zelador

    You are evaluating a new MVP concept called “O Zelador” (ZELADOR).

    The idea is a hybrid guest-host residency model designed for furnished rental properties.

    Here’s the core concept:

    • A resident (typically a recurring guest or someone seeking a stable address) is offered discounted rent in a fully furnished unit.
    • In exchange, they take on recurring daily property management and hosting responsibilities (similar to an on-site host or caretaker).
    • This creates a “guest-host” role—part tenant, part operator.
    • The resident may also have opportunities to earn income from home, tied to managing or supporting the property.
    • Each property (or cohort of units) has limited slots (typically one) to maintain control and quality, and profitability.

    The value proposition:

    • For the resident: lower housing costs + income opportunity + stable address
    • For the operator: built-in, on-site management + reduced operational overhead

    Constraints / open questions:

    • Legal structure (tenant vs. contractor vs. hybrid)
    • Liability and compliance
    • Scope of responsibilities and incentives

    Goal of this MVP:

    • Test how compelling and understandable this concept is to potential users before building it.

    Please evaluate:

    1. Does this concept make intuitive sense?
    2. What are the biggest risks or points of confusion?
    3. Who is the ideal early adopter?
    4. Would you engage with or test this offering? Why or why not?

    Comment below