Website review, no card needed

partyrentalltd.com logo

partyrentalltd.com website review

Visit site (opens in a new tab)Reviewed 20 November 202635 issues · 86 checks

This review found 35 issues worth fixing on partyrentalltd.com, 17 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.1 s957 msMay 30Nov 141.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.6 s
Jul 18, 20261.3 s
Jul 25, 20261.2 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Nov 14, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
91 ms78 msMay 30Nov 1487 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202679 ms
Jun 6, 202683 ms
Jun 13, 202680 ms
Jun 20, 202684 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202688 ms
Jul 18, 202689 ms
Jul 25, 202687 ms
Aug 1, 202688 ms
Aug 8, 202687 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202684 ms
Sep 19, 202681 ms
Sep 26, 202682 ms
Oct 3, 202685 ms
Oct 10, 202684 ms
Oct 17, 202686 ms
Oct 24, 202684 ms
Oct 31, 202684 ms
Nov 7, 202686 ms
Nov 14, 202687 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of partyrentalltd.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. partyrentalltd.com at 0.4 s0.4 s
  2. partyrentalltd.com at 0.8 s0.8 s
  3. partyrentalltd.com at 1.2 s1.2 s
  4. partyrentalltd.com at 1.6 s1.6 s
  5. partyrentalltd.com at 1.9 s1.9 s
  6. partyrentalltd.com at 2.3 s2.3 s
  7. partyrentalltd.com at 2.7 s2.7 s
  8. partyrentalltd.com at 3.1 s3.1 s

Speed

12 to fix40
  • Reduce unused JavaScript

    9.3 s · 2.6 MB

    About 2.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.3 s faster on a phone.

  • Use efficient cache lifetimes

    6.6 s · 2.0 MB

    37 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

  • Render-blocking requests

    4.8 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.

  • Improve image delivery

    1.9 s · 592 KiB

    21 images could be 592 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Reduce unused CSS

    1.2 s · 224 KiB

    About 224 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, zoom.us and New Relic and others), adding 3.5 MB and 676 ms of main-thread time.

  • Minify JavaScript

    600 ms · 418 KiB

    418 KiB could be saved by minifying JavaScript.

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 458 ms. During a long task the page ignores taps.

  • Google Tag Manager adds 381 ms

    381 ms

    Google Tag Manager costs a phone 381 ms of main-thread work and 673 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • zoom.us adds 165 ms

    165 ms

    zoom.us costs a phone 165 ms of main-thread work and 2.6 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 2.5 s

    A phone's processor spends 2.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Document request latency

    50 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

1 checks passed
  • Server response: 71 ms

    71 ms

    Your server sent the HTML in 71 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 34.4 s

    34.4 s

    Your largest element takes 34.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Gold holiday linen tabletop setting with plum napkins and l…”.

  • Time to Interactive: 39.2 s

    39.2 s

    The page becomes fully interactive after 39.2 s. Good is under 3.8 s.

  • First Contentful Paint: 5.8 s

    5.8 s

    The first text or image appears after 5.8 s on a phone. Good is under 1.8 s.

  • Speed Index: 9.8 s

    9.8 s

    Visually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 660 ms

    660 ms

    Scripts block taps and scrolling for 660 ms in total while the page loads. Good is under 200 ms.

  • 44 images without width and height

    44 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 79 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

    Real visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 91 ms

    91 ms

    Real visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 551 ms

    551 ms

    Real visitors wait 551 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 41% faster for real visitors

    -41%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 8.2 MB in 102 requests

    8.2 MB

    Your homepage downloads 8.2 MB in 102 requests on a phone: scripts 4.1 MB (30), images 3.0 MB (31) and other files 734 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 22 images in older formats

    22 images (1.0 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 4 images below the first screen load straight away

    4 images further down the page (237 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.3 g of CO₂ per visit

    2.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.32 g of CO₂e: 278.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8893
  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9272
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (24 characters)

    Your title is only 24 characters: “Home - Party Rental Ltd.”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 85 internal links, 20 external

    The homepage links to 85 pages on partyrentalltd.com and 20 external pages.

3 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Party Rental Ltd. is a full-service party rental company, renting special event items and equipment along the East Coas…”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.partyrentalltd.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.partyrentalltd.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (284 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.partyrentalltd.com/products/5020 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://www.partyrentalltd.com/products/5020, https://www.partyrentalltd.com/products/bars-back-bars-and-bar-carts/163845 and https://www.partyrentalltd.com/products/food-service/5172 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    45 of 45 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Only about 192 words

    The homepage has only about 192 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

5 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Log in/Register”, “Track Your Order” and “Order Linen Swatches”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 6 of them by other companies (measured from a US location before any click).

  • 36 other companies contacted

    Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at partyrentalltd.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Verizon Business

Company

Employees
396

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on partyrentalltd.com, including 18 speed issues, 5 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25