Loading Report View…
0/ 100
pinebookpublishing.com Website Audit Report
pinebookpublishing.com scored 67 out of 100 in this SavageAudit website audit covering Performance, SEO, Design, Copy, User Experience, and Conversion. The report uses captured website evidence to explain what is working, what is limiting the experience, and which improvements deserve attention first.
“A manuscript gatekeeper with a clogged driveway and a confused desk.”
Pine Book Publishing has the energy of a serious book outfit that got mugged by its own homepage. The copy is trying to reassure authors, but the page keeps tripping over itself like a sales rep wearing roller skates in a library.
https://pinebookpublishing.com/
TECHNICAL SUMMARY
The fundamentals are half-working and half-dragging a suitcase full of JS. Core performance is held back by an 11.0 s LCP, 16.6 s interactive time, 850 ms of blocking time, and 3,375 KiB of page weight, while 631 KiB of unused JavaScript and 801 KiB of image savings are just sitting there like free money nobody picked up. SEO is mostly intact with canonical and crawlability in place, but 63 missing image alts, skipped heading levels, and 6 console errors—including broken marketing and IP lookup requests—make the page look less like a publishing authority and more like a demo that forgot to clean up after itself.
Where It Burns
6 categoriesWebsite Audit Findings for pinebookpublishing.com
SavageAudit identified 36 visible findings and recommendations across 6 audit categories. Each section below combines the category score with observed evidence and prioritized fixes.
5201 PERFORMANCELCP 11.0 s7902 SEOConsole Errors 66503 DESIGNImages 1478204 COPYWord Count 2,4685405 UXConsole Errors 68106 CONVERSIONCTA Count 21
01
PERFORMANCE AUDIT
52
LCP11.0 sInteractive16.6 sTotal Byte Weight3,375 KiBUnused JavaScript Savings631 KiB
- 🔥An 11.0 s LCP on a book publishing homepage is longer than most authors spend rereading their pitch emails.
💀
The page is dragging a publishing opportunity behind a truck and calling it a launch.
- →Compress hero images and switch them to WebP/AVIF so the homepage stops arriving like a late manuscript.LCP: 11.0 sImpact: highEffort: medium
Why this matters
An 11.0 s LCP points directly at oversized hero content slowing the first meaningful view.
- →Defer non-critical JavaScript and cut render-blocking resources before the page keeps the author waiting in the lobby.TBT: 850 msImpact: highEffort: medium
Why this matters
850 ms of blocking time means scripts are freezing the main thread long enough to hurt responsiveness.
- →Enable CDN caching and long cache TTLs for static assets so repeat visitors aren’t re-downloading the same publishing boulder.FCP: 1.2 sImpact: mediumEffort: low
Why this matters
FCP is decent, but better caching helps keep early paint fast as asset weight stays high.
02
SEO AUDIT
79
Console Errors6Missing WebSite SchemaYesHeading Level Skipsh1->h4, h2->h4Twitter CardMissing
- 🔥You’ve got 2 JSON-LD blocks and 0 parse errors, which is nice—then the page forgets WebSite schema like it left the ISBN off the dust jacket.
💀
The search signals are mostly standing, but the page keeps dropping important metadata on the floor.
- →Add descriptive alt text to every meaningful image so search and accessibility stop guessing what 63 visuals are supposed to be.Missing Alt: 63Impact: mediumEffort: medium
Why this matters
63 missing alts is a large share of image content left invisible to both users and crawlers.
- →Publish llms.txt or ai.txt with your priority URLs and support paths so AI crawlers don’t have to improvise your publishing catalog.AI Hints: MissingImpact: mediumEffort: medium
Why this matters
The site has no AI hint file, so priority content is less discoverable to AI crawlers.
- →Add a twitter:card tag and companion metadata so shared manuscript and author pages don’t preview like a blank audition tape.Twitter Card: MissingImpact: lowEffort: low
Why this matters
Without a Twitter card, social previews are less controlled and less clickable.
03
DESIGN AUDIT
65
Images147Headings188Missing Alt63Font Families7
- 🔥147 images and 188 headings on one page is not layout, it’s a publishing convention center with no floor plan.
💀
The page looks like three design systems and a panic attack shared the same stylesheet.
- →Add supporting imagery so the layout feels intentional instead of overcrowded by 147 visual elements.Images: 147Impact: mediumEffort: medium
Why this matters
A high image count needs deliberate composition or it starts reading as visual clutter.
- →Fix missing alt text to pass accessibility audits and stop 63 images from becoming decorative ghosts.Missing Alt: 63Impact: mediumEffort: medium
Why this matters
Missing alt text weakens accessibility and makes image-heavy sections less usable.
- →Reduce font families from 7 to 2-3 so the page stops looking like it dressed in someone else’s publishing closet.Font Families: 7Impact: mediumEffort: low
Why this matters
Seven font families create inconsistency and visual noise across the page.
04
COPY AUDIT
82
Word Count2,468Sentence Count143CTA Count21H1 Count1
- 🔥One H1 is good, but the title and meta description both start with 'Best Book Publishing company' like the page is shouting its own resume into the void.
💀
The copy is confident, verbose, and occasionally one typo away from sounding like a brochure with stage fright.
- →Tighten the headline so the manuscript-to-market promise lands in one sentence instead of circling the runway.H1 Count: 1Impact: mediumEffort: low
Why this matters
A single H1 is fine, but the page still needs a clearer value statement to do its job fast.
- →Break long paragraphs into skimmable bullets and shorter sentences so authors can find the publishing process before their coffee goes cold.Avg Words/Sentence: 17Impact: lowEffort: medium
Why this matters
At 17 words per sentence on average, readability can be improved for faster scanning.
- →Make the primary CTA stand out because 21 CTAs on one page turns the call-to-action into background noise.CTA Count: 21Impact: mediumEffort: low
Why this matters
Too many CTAs dilute the main action and make the next step less obvious.
05
UX AUDITUSER EXPERIENCE AUDIT
54
Console Errors6Broken Assets12CLS0.076Long Tasks16
- 🔥6 console errors plus 12 broken assets means the page isn’t just rough around the edges—it’s actively dropping tools on authors’ feet.
💀
The user experience is a hallway full of spilled boxes, and some of them are on fire.
- →Fix client-side JavaScript errors so interactions don’t fail silently while authors try to contact you.JS Errors: 6Impact: highEffort: medium
Why this matters
Six console errors indicate real runtime failures that can break interactions and undermine reliability.
- →Repair failed asset URLs and deployment paths so scripts, images, and stylesheets stop disappearing mid-process.Broken Assets: 12Impact: highEffort: medium
Why this matters
Twelve broken assets can directly damage page behavior, visuals, and loading stability.
- →Reduce form fields to the essentials so the contact journey doesn’t feel like a tax return for writers.Form Fields: 14Impact: mediumEffort: medium
Why this matters
Fourteen required fields add unnecessary effort to the primary contact flow.
06
CONVERSION AUDIT
81
CTA Count21Forms3Required Inputs14Social Proof Count4
- 🔥21 CTAs should be persuasive, but here they read like a committee trying to sell one manuscript with twenty voices.
💀
The site wants leads, but it’s making authors fill out forms like they’re applying for citizenship.
- →Add a primary CTA above the fold that matches the core offer so visitors don’t have to hunt through 21 competing prompts.CTA Count: 21Impact: mediumEffort: low
Why this matters
A high CTA count without a clear primary action weakens the conversion path.
- →Offer a low-friction contact option like a visible email or simpler form so the page stops acting like contact is a privilege.Contact Path: PresentImpact: lowEffort: medium
Why this matters
Even with a contact path present, the flow needs to be easier and more visible.
- →Move testimonials, logos, or book stats closer to the CTA because 4 social proof items need better placement to do their job.Social Proof: 4Impact: mediumEffort: low
Why this matters
Social proof works best when it supports the decision right next to the action button.
Audit overview
pinebookpublishing.com Audit Summary
The fundamentals are half-working and half-dragging a suitcase full of JS. Core performance is held back by an 11.0 s LCP, 16.6 s interactive time, 850 ms of blocking time, and 3,375 KiB of page weight, while 631 KiB of unused JavaScript and 801 KiB of image savings are just sitting there like free money nobody picked up. SEO is mostly intact with canonical and crawlability in place, but 63 missing image alts, skipped heading levels, and 6 console errors—including broken marketing and IP lookup requests—make the page look less like a publishing authority and more like a demo that forgot to clean up after itself.
Based on the category scores in this report, Copy is the strongest area while Performance has the most room for improvement.
How SavageAudit Evaluated pinebookpublishing.com
SavageAudit evaluated the public website at https://pinebookpublishing.com/ across performance, technical SEO, design, copy, user experience, and conversion signals. Scores and recommendations reflect the website evidence available when this audit was generated on May 30, 2026.
Similar Website Audit Reports
Compare this result with other public SavageAudit reports that received a similar overall website score.