Website review, no card needed
ieee-pes.org website review
Visit site (opens in a new tab)Reviewed 3 November 202638 issues · 88 checks
This review found 38 issues worth fixing on ieee-pes.org, 13 of them high impact, across 88 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 171 ms |
| May 23, 2026 | 169 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 181 ms |
| Jun 13, 2026 | 184 ms |
| Jun 20, 2026 | 189 ms |
| Jun 27, 2026 | 181 ms |
| Jul 4, 2026 | 187 ms |
| Jul 11, 2026 | 180 ms |
| Jul 18, 2026 | 175 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 165 ms |
| Aug 8, 2026 | 173 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 221 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 234 ms |
| Sep 12, 2026 | 224 ms |
| Sep 19, 2026 | 221 ms |
| Sep 26, 2026 | 226 ms |
| Oct 3, 2026 | 232 ms |
| Oct 10, 2026 | 237 ms |
| Oct 17, 2026 | 247 ms |
| Oct 24, 2026 | 251 ms |
| Oct 31, 2026 | 244 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
Speed
Render-blocking requests
3.1 s64 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
FontAwesome CDN adds 1.0 s
1.0 sFontAwesome CDN costs a phone 1.0 s of main-thread work and 239 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 6.4 s
A phone's processor spends 6.4 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (FontAwesome CDN, Google Tag Manager and Facebook and others), adding 1.4 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
300 ms · 741 KiBAbout 741 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.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 237 KiBAbout 237 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 474 ms
474 msGoogle Tag Manager costs a phone 474 ms of main-thread work and 641 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.
Improve image delivery
373 KiB6 images could be 373 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Facebook adds 310 ms
310 msFacebook costs a phone 310 ms of main-thread work and 278 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.
Use efficient cache lifetimes
323 KiB14 files are served with short cache lifetimes, so returning visitors download them again (323 KiB).
2,472 HTML elements
The page has 2,472 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 198 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 5 KiB5 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
20 KiB20 KiB JavaScript is shipped twice across bundles.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Time to Interactive: 21.4 s
21.4 sThe page becomes fully interactive after 21.4 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.0 s
4.0 sThe first text or image appears after 4.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 814 ms
814 msScripts block taps and scrolling for 814 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 291 ms
291 msReal visitors wait 291 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 46% slower for real visitors
+46%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 171 ms to 244 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 4.0 s
4.0 sYour largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “IEEE PES events are open for registration for both members …”. Most of its time is element render delay (3.3 s).
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 198 requests
4.4 MBYour homepage downloads 4.4 MB in 198 requests on a phone: scripts 1.8 MB (68), images 1.7 MB (26) and fonts 386 KiB (13). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (534 KiB) 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.
About 1.3 g of CO₂ per visit
1.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.25 g of CO₂e: 150.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA roles used must conform to valid values (1 element)
ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Elements must only use permitted ARIA attributes (5 elements)
Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (29 elements)
All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
101 internal links, 45 external
The homepage links to 101 pages on ieee-pes.org and 45 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “We're a nonprofit, member driven org, with a mission to be the leading provider of scientific & engineering information…”.
Title: 47 characters
Your title is a healthy 47 characters: “IEEE Power and Energy Society (IEEE PES) | Home”.
Canonical URL set
The canonical URL is https://ieee-pes.org/.
Structured data in place
Structured data found: BreadcrumbList, Event, ImageObject, Organization and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://ieee-pes.org/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://ieee-pes.org/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 (1,085 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://ieee-pes.org/about-pes/member-profiles and https://ieee-pes.org/climate-change have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages slow to respond
https://ieee-pes.org/about-pes, https://ieee-pes.org/about-pes/2026-governing-board, https://ieee-pes.org/about-pes/society-committees, https://ieee-pes.org/about-pes/strategic-partnerships, https://ieee-pes.org/about-pes/member-profiles and https://ieee-pes.org/climate-change took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 75 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cookie-consent.ieee.org/ieee-cookie-banner.css' from origin 'https://ieee-pes.org'…”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
13 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 565 words of copy
The homepage carries about 565 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “RESERVE NOW”.
15 calls to action
The homepage has 15 calls to action, for example “Join IEEE”, “LEARN MORE” and “Join IEEE PES”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 trust badge and “40K members”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and The Trade Desk (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) 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 ieee-pes.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on ieee-pes.org, including 23 speed issues, 2 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.