Website review, no card needed
coneyislandprep.org website review
Visit site (opens in a new tab)Reviewed 28 October 202639 issues · 86 checks
This review found 39 issues worth fixing on coneyislandprep.org, 21 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 96 ms |
| May 23, 2026 | 99 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 89 ms |
| Jun 27, 2026 | 94 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 103 ms |
| Jul 18, 2026 | 95 ms |
| Aug 8, 2026 | 81 ms |
| Aug 15, 2026 | 86 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 89 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 108 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
38.6 s · 8.1 MB6 images could be 8.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 38.6 s faster on a phone.
Reduce unused JavaScript
4.7 s · 943 KiBAbout 943 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 297 KiB18 files are served with short cache lifetimes, so returning visitors download them again (297 KiB).
Render-blocking requests
1.5 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 34
34/100Your mobile performance score is 34 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.3 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 (Google Tag Manager, Hotjar and Accessibe Accessibility Overlay and others), adding 20.6 MB and 1.4 s of main-thread time.
Vimeo adds 156 ms
156 msVimeo costs a phone 156 ms of main-thread work and 19.3 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 CSS
600 ms · 53 KiBAbout 53 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 573 ms
573 msGoogle Tag Manager costs a phone 573 ms of main-thread work and 570 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 320 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Real-user CLS: 0.27
0.27For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 61.1 s
61.1 sYour largest element takes 61.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Commitment to Succeed. We proudly serve a diverse array…”.
Time to Interactive: 61.3 s
61.3 sThe page becomes fully interactive after 61.3 s. Good is under 3.8 s.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 96 ms to 108 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 108 ms
108 msReal visitors wait 108 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 743 ms
743 msReal visitors wait 743 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 29.9 MB in 127 requests
29.9 MBYour homepage downloads 29.9 MB in 127 requests on a phone: other files 18.8 MB (44), images 9.0 MB (20) and scripts 2.0 MB (46). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
FY26-SD-Post-1-scaled.png weighs 6.2 MB. On a phone connection a single image that size takes seconds.
5 images far larger than shown
6.2 MB5 images are downloaded at several times the size a phone draws them, for example FY26-SD-Post-1-scaled.png at 2,560 px wide, shown at 390 px. Resized copies would save about 6.2 MB.
6 images in older formats
6 images (7.9 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.
6 images below the first screen load straight away
6 images further down the page (7.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 8.5 g of CO₂ per visit
8.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.48 g of CO₂e: 1017.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h1 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (24 characters)
Your title is only 24 characters: “Home - Coney Island Prep”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“The Courage to Dream.” and “The Commitment to Succeed.”). One clear main headline is easier for people and search engines.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
37 internal links, 13 external
The homepage links to 37 pages on coneyislandprep.org and 13 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://coneyislandprep.org/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://coneyislandprep.org/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://coneyislandprep.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (638 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://coneyislandprep.org/about-us, https://coneyislandprep.org/about-us/our-approach, https://coneyislandprep.org/about-us/impact, https://coneyislandprep.org/about-us/leadership, https://coneyislandprep.org/about-us/diversity-equity-inclusion and https://coneyislandprep.org/about-us/cip-news and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 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
4 small tap targets
4 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 616 words of copy
The homepage carries about 616 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Us” and “Contact”.
Analytics in place
Analytics detected: Google Analytics, Hotjar, HubSpot and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 5 phone links and 5 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 1 more (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 2 of them by other companies (measured from a US location before any click).
37 other companies contacted
Loading the homepage contacts 37 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 coneyislandprep.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Hotjar
- Hosting
- Google Cloud
Hiring
- Hiring
- 7 open roles
- Teams
- 2026-2027 Teacher (4), College Team (1)
- Job board
- greenhouse
- Careers page
- coneyislandprep.org/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on coneyislandprep.org, including 20 speed issues, 3 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.