Website review, no card needed
emjcorp.com website review
Visit site (opens in a new tab)Reviewed 3 November 202640 issues · 86 checks
This review found 40 issues worth fixing on emjcorp.com, 16 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.8 s |
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.7 s
3.0 s
Speed
Improve image delivery
9.9 s · 2.8 MB10 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.9 s faster on a phone.
Reduce unused JavaScript
4.0 s · 910 KiBAbout 910 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
2.3 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 23
23/100Your mobile performance score is 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, YouTube and Bootstrap CDN and others), adding 1.4 MB and 979 ms of main-thread time.
Google Tag Manager adds 593 ms
593 msGoogle Tag Manager costs a phone 593 ms of main-thread work and 645 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.
YouTube adds 381 ms
381 msYouTube costs a phone 381 ms of main-thread work and 761 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 253 ms. During a long task the page ignores taps.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 885 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
150 ms · 8 KiB8 KiB could be saved by minifying JavaScript.
Legacy JavaScript
50 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 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.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 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.
Largest Contentful Paint: 34.7 s
34.7 sYour largest element takes 34.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video Player Media error: Format(s) not supported or source…”.
Time to Interactive: 35.6 s
35.6 sThe page becomes fully interactive after 35.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.778
0.778The layout shifts by 0.778 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 706 ms
706 msScripts block taps and scrolling for 706 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 13.4 MB in 81 requests
13.4 MBYour homepage downloads 13.4 MB in 81 requests on a phone: images 6.4 MB (17), media 5.1 MB (1) and scripts 1.5 MB (32). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 3.3 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
957 KiB4 images are downloaded at several times the size a phone draws them, for example 20230402-PAM-Health-Miamisburg-Exterior-002-scaled-aspect-ra at 2,880 px wide, shown at 390 px. Resized copies would save about 957 KiB.
13 images in older formats
13 images (5.2 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.
7 images below the first screen load straight away
7 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.8 g of CO₂ per visit
3.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.79 g of CO₂e: 455.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
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.
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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 (h2 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
22 internal links, 5 external
The homepage links to 22 pages on emjcorp.com and 5 external pages.
8 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “EMJ is committed to elevating client experience. We challenge our clients to expect more from their commercial construc…”.
One H1 headline
Your main headline reads: “Expect More From YourConstruction Experience”.
Title: 64 characters
Your title is a healthy 64 characters: “EMJ Construction | Expect More From Your Construction Experience”.
Canonical URL set
The canonical URL is https://www.emjcorp.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://www.emjcorp.com/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://www.emjcorp.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 (381 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.emjcorp.com/project/us-xpress-truck-terminal has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.emjcorp.com/from-finance-to-construction-michelle-sapps-inspiring-journey-%f0%9f%8f%97%ef%b8%8f, whose canonical is https://www.emjcorp.com/from-finance-to-construction-michelle-sapps-inspiring-journey-%F0%9F%8F%97%EF%B8%8F. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages with very little text
https://www.emjcorp.com/news, https://www.emjcorp.com/contact-us, https://www.emjcorp.com/project/encore-novo-modern-apartments and https://www.emjcorp.com/project/us-xpress-truck-terminal have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
19 small tap targets
19 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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.
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.
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 548 words of copy
The homepage carries about 548 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “Learn More”.
Analytics in place
Analytics detected: Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
4 cookies set on arrival
4Opening the homepage sets 4 cookies, 1 of them by other companies (measured from a US location before any click).
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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 emjcorp.com, 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
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on emjcorp.com, including 18 speed issues, 1 SEO issue 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.