Shop website photos: set a page budget before uploading the originals: working record
Use this six-field worksheet to balance visual evidence and loading cost through a page-specific photo inventory and before-after check.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Page and image | Customer purpose | Displayed size | File and delivery evidence | Proposed change | Visual and loading retest |
|---|---|---|---|---|---|
| Illustrative: service hero photo | Show actual installation detail | Phone and desktop crops | Original oversized request observed | Create suitable delivered variant |
- The starting row is fictional, not merchant evidence. Replace it with your own verified record. Blank fields remain unresolved.
- Create one row per decision or observation described in the article. Use the worked example to understand the method, not as proof about your business.
- Record exact public URLs and collection dates where relevant. Unknown, failed and not checked are different from a verified pass.
- Keep customer information, account credentials and private documents outside this worksheet. Use role names or internal references.
- A completed row does not prove publication, authorization, indexing, rankings or revenue. Record the actual acceptance check separately.
- Export the record to approved business storage if needed. Browser edits are cleared on reload.
A clear photo of your shop is helpful. Sending a full-resolution camera original to every phone visitor usually is not necessary to make that photograph useful. Review what each image contributes and how it is delivered before removing the visuals that help customers understand the work.
Use with this guide
website audit tool
Review the current scope and workflow for website audit tool.
business website tool
Review the current scope and workflow for business website tool.
Collect wrap installation photos with clear customer permission
A photo approved for the customer’s project record is not automatically approved for your next advertisement. Record the intended use before publishing.
Start with the page’s visual job
Separate images that prove or explain something from decorative images that repeat the same idea. An exterior photo helps a first-time visitor recognize the building, while a project detail helps a wrap buyer inspect the kind of work. A big generic background? It may add very little. Google recommends relevant, clear images near the text they support, and notes that images often make up much of a page’s size. The website audit tool can organize supported performance findings, but the owner should decide which visual evidence matters. A faster page isn’t automatically a better service page if it removes information customers need.
Sources for this section: Google Search Central: image best practices
Compare the delivered file with its display role
Ask your developer or website editor to check the actual image request and the size it shows on different screens. Responsive delivery can serve the right-sized files without sacrificing quality. Keep the original safe for future edits, but don’t assume every visitor needs that same file. The business website tool supports photo management and previews where enabled. Check what image processing it really offers. Don’t assume every upload gets optimized automatically. Then check crops at phone, tablet, and desktop widths. A fast-loading image still fails the acceptance test if it cuts off the work or signage that matters.
Sources for this section: Google Search Central: image best practices
Use an image budget example carefully
Suppose an illustrative service page sends eight images, each around two megabytes. Images alone use about 16 megabytes, before scripts, fonts, and everything else. If suitable delivered versions average 200 kilobytes, the eight together use about 1.6 megabytes. That’s transfer-size math, not a promise of faster loading or better rankings. Quality, file formats, browser behavior, and connection conditions all matter. Check the page after you make the change. Smaller files still need to answer the customer’s question. And don’t force one file-size target on every hero, logo, thumbnail, and detailed project image.
Sources for this section: Google Search Central: image best practices
Measure the behavior the customer experiences
Google’s Core Web Vitals cover loading, responsiveness, and layout stability. First, record the issue the audit actually found. Don’t call every warning “slow photos.” A layout shift may need dimensions or layout work. Delayed interaction may have nothing to do with images. Compare the same page under the same test conditions before and after a focused repair. And don’t treat one lab score as a revenue forecast or a full accessibility assessment. Keep image-search metadata honest, too. Descriptive filenames and alt text should match the photo’s actual subject, not cram in unrelated locations and service keywords.
Sources for this section: Google Search Central: Core Web Vitals
Use the page-photo budget worksheet
Give each meaningful image its own row, and say what it does for customers. Record its displayed role, what you observed about delivery, and the change you propose. Use real measurements when you have them. Mark unknowns. Don’t make them up. Add both a visual retest and a loading retest. They matter. Keep licensing and permission records separate. This worksheet helps the owner and developer pick a proportionate fix. There is no need to delete every image or buy a new website over one score. BlueFinch’s eligible audit service organizes findings, but doesn’t guarantee search positions, speed on every device, or a specific sales result.
Keep a before-and-after file reference for every changed image. If the smaller version loses important detail, the reviewer can restore or revise it without hunting down the original again. This really helps with project photos where the finish, edge or installation detail is the whole point.
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
Use this page for general business information. It is not legal, tax, or accounting advice.