Website review, no card needed

phillipsedison.com logo

phillipsedison.com website review

Visit site (opens in a new tab)Reviewed 19 November 202629 issues · 61 checks

This review found 29 issues worth fixing on phillipsedison.com, 11 of them high impact, across 61 checks. The most urgent: improve image delivery. 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
3.6 s2.0 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.3 s
Jul 4, 20263.3 s
Jul 11, 20263.2 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.6 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Nov 7, 20262.4 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
169 ms108 msMay 30Nov 14130 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026154 ms
Jun 6, 2026158 ms
Jun 13, 2026162 ms
Jun 20, 2026160 ms
Jun 27, 2026146 ms
Jul 4, 2026129 ms
Jul 11, 2026122 ms
Jul 18, 2026115 ms
Jul 25, 2026120 ms
Aug 1, 2026122 ms
Aug 8, 2026119 ms
Aug 15, 2026121 ms
Aug 22, 2026127 ms
Aug 29, 2026129 ms
Sep 5, 2026133 ms
Sep 12, 2026135 ms
Sep 19, 2026136 ms
Sep 26, 2026128 ms
Oct 3, 2026137 ms
Oct 10, 2026132 ms
Oct 17, 2026129 ms
Oct 24, 2026132 ms
Oct 31, 2026130 ms
Nov 7, 2026129 ms
Nov 14, 2026130 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 phillipsedison.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. phillipsedison.com at 0.4 s0.4 s
  2. phillipsedison.com at 0.8 s0.8 s
  3. phillipsedison.com at 1.1 s1.1 s
  4. phillipsedison.com at 1.5 s1.5 s
  5. phillipsedison.com at 1.9 s1.9 s
  6. phillipsedison.com at 2.3 s2.3 s
  7. phillipsedison.com at 2.6 s2.6 s
  8. phillipsedison.com at 3.0 s3.0 s

Speed

7 to fix62
  • Improve image delivery

    36.3 s · 17.1 MB

    13 images could be 17.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 36.3 s faster on a phone.

  • Use efficient cache lifetimes

    7.4 MB

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Azure Web Services), adding 7.4 MB and 0 ms of main-thread time.

  • Azure Web Services adds 0 ms

    0 ms

    Azure Web Services costs a phone 0 ms of main-thread work and 7.4 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.

  • Reduce unused JavaScript

    300 ms · 71 KiB

    About 71 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Render-blocking requests

    300 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 14 KiB

    Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 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.

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 516 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 91.3 s

    91.3 s

    Your largest element takes 91.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 94.6 s

    94.6 s

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

  • Speed Index: 12.0 s

    12.0 s

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

11 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: 2.4 s

    2.4 s

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

  • Real-user INP: 131 ms

    131 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 764 ms

    764 ms

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

  • Tap response (INP) got 17% faster for real visitors

    -17%

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

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

    -28%

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

  • Total Blocking Time: 198 ms

    198 ms

    Scripts block the page for only 198 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix28
  • Page weight: 29.1 MB in 56 requests

    29.1 MB

    Your homepage downloads 29.1 MB in 56 requests on a phone: images 20.0 MB (17), media 6.4 MB (1) and other files 1.6 MB (3). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    2.3 MB

    4 images are downloaded at several times the size a phone draws them, for example 010228_001.jpg at 2,048 px wide, shown at 278 px. Resized copies would save about 2.3 MB.

  • 4 images below the first screen load straight away

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

  • About 8.2 g of CO₂ per visit

    8.24 g

    By the Sustainable Web Design model, a visit to your homepage emits about 8.24 g of CO₂e: 988.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 use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

1 to fix100
  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

SEO

5 to fixGoogle 10077
  • No H1 headline

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

  • 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, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

4 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Phillips Edison & Company is one of the largest real estate investment trusts in the shopping and grocery sector. Let u…”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Leading Real Estate Investment Trust | PECO”.

  • 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.phillipsedison.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 395 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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.

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.

  • llms.txt published

    The site publishes https://www.phillipsedison.com/llms.txt (8 KiB, 0 links), a plain-text guide to the site for AI tools.

Best practices

3 to fixGoogle 9285
  • 26 small tap targets

    26 of 51 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 12 distorted images

    12 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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.

  • About 395 words of copy

    The homepage carries about 395 words of visible text.

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try the NEW AI Search”.

Privacy and tracking

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 phillipsedison.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
Next.js
Hosting
Azure

Hiring

Hiring
1 open role
Job board
careers page

Company

Founded
1991
Headquarters
Cincinnati

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on phillipsedison.com, including 10 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