Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Metrics
First Contentful Paint
1.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive
1.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index
1.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Largest Contentful Paint
3.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Show audits relevant to:
Opportunities
Opportunity
Estimated Savings
Serve images in next-gen formats 5.18 s
Serve images in next-gen formats
5.18 s
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
URL | Resource Size | Potential Savings | |
|---|---|---|---|
Next <img src="images/home2.png" alt="Next"> | /images/home2.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 594.7 KiB | 553.9 KiB |
Previous <img src="images/customer-profile.png" alt="Previous"> | /images/customer-profile.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 391.6 KiB | 359.2 KiB |
CodePsych <img src="images/logo-tp.png" alt="CodePsych" class="logo-img"> | /images/logo-tp.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 102.8 KiB | 73.8 KiB |
Portfolio preview <img src="images/home1.png" alt="Portfolio preview" id="lightboxImage"> | /images/home1.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 101.8 KiB | 57.3 KiB |
Eliminate render-blocking resources 0.63 s
Eliminate render-blocking resources
0.63 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.FCPLCP
URL | Transfer Size | Potential Savings |
|---|---|---|
/css2?family=… (fonts.googleapis.com) | 1.4 KiB | 780 ms |
Properly size images 0.6 s
Properly size images
0.6 s
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
URL | Resource Size | Potential Savings | |
|---|---|---|---|
body > header.hero > div.hero-bg > img.hero-logo-bg <img src="images/logo-tp.png" alt="" class="hero-logo-bg" aria-hidden="true"> | /images/logo-tp.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 102.8 KiB | 60.6 KiB |
Portfolio preview <img src="images/home1.png" alt="Portfolio preview" id="lightboxImage"> | /images/home1.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 101.8 KiB | 57.0 KiB |
Diagnostics
Image elements do not have explicit width and height
width and height Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn moreCLS
URL | |
|---|---|
Portfolio preview <img src="images/home1.png" alt="Portfolio preview" id="lightboxImage"> | /images/home1.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) |
Avoid chaining critical requests 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.FCPLCP
Maximum critical path latency: 370 ms
Initial Navigation
/css2?family=…
(fonts.googleapis.com)
…v20/UcC73FwrK….woff2
- 90 ms, 47.83 KiB (fonts.gstatic.com)
…v40/nuFiD-vYS….woff2
- 110 ms, 37.69 KiB (fonts.gstatic.com)
/css/style.css
- 40 ms, 5.54 KiB (69c14b8d695f25143572f5b8--codepsych.netlify.app)
/js/main.js
- 70 ms, 4.16 KiB (69c14b8d695f25143572f5b8--codepsych.netlify.app)
Keep request counts low and transfer sizes small 10 requests • 1,295 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type | Requests | Transfer Size |
|---|---|---|
Total | 10 | 1,294.8 KiB |
Image | 4 | 1,192.1 KiB |
Font | 2 | 85.5 KiB |
Stylesheet | 2 | 6.9 KiB |
Document | 1 | 6.1 KiB |
Script | 1 | 4.2 KiB |
Media | 0 | 0.0 KiB |
Other | 0 | 0.0 KiB |
Third-party | 3 | 86.9 KiB |
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element |
|---|
Full-stack development for businesses ready to stand out online. Custom website… <p class="hero-subtitle"> |
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element | CLS Contribution |
|---|---|
Available for new projects <div class="hero-badge"> | 0 |
CodePsych <span class="logo-text"> | 0 |
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn moreTBT
URL | Start Time | Duration |
|---|---|---|
888 ms | 195 ms | |
798 ms | 90 ms | |
1,202 ms | 69 ms | |
1,083 ms | 64 ms | |
1,147 ms | 55 ms |
Passed audits (31) Show Hide
Passed audits (31)
Show Hide
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.FCPLCP
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
Preconnect to required origins Warnings: A `<link rel=preconnect>` was found for "https://fonts.gstatic.com" but was not used by the browser. Check that you are using the `crossorigin` attribute properly.
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.FCPLCP
Initial server response time was short Root document took 60 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.FCPLCP
URL | Time Spent |
|---|---|
60 ms |
Avoid multiple page redirects
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.FCPLCP
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn moreLCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn MoreTBT
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.LCP
Avoids enormous network payloads Total size was 1,295 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
URL | Transfer Size |
|---|---|
/images/home2.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 595.2 KiB |
/images/customer-profile.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 392.0 KiB |
/images/logo-tp.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 103.0 KiB |
/images/home1.png (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 102.0 KiB |
…v20/UcC73FwrK….woff2 (fonts.gstatic.com) | 47.8 KiB |
…v40/nuFiD-vYS….woff2 (fonts.gstatic.com) | 37.7 KiB |
6.1 KiB | |
/css/style.css (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 5.5 KiB |
/js/main.js (69c14b8d695f25143572f5b8--codepsych.netlify.app) | 4.2 KiB |
/css2?family=… (fonts.googleapis.com) | 1.4 KiB |
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoids an excessive DOM size 342 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.TBT
Statistic | Element | Value |
|---|---|---|
Total DOM Elements | 342 | |
Maximum DOM Depth | div.feature > div.feature-icon > svg > path <path d="M12 2L2 7l10 5 10-5-10-5zM2 17l10 5 10-5M2 12l10 5 10-5"> | 10 |
Maximum Child Elements | body <body> | 11 |
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
JavaScript execution time 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.TBT
URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
1,345 ms | 12 ms | 2 ms | |
Unattributable | 78 ms | 4 ms | 0 ms |
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn moreTBT
Category | Time Spent |
|---|---|
Rendering | 596 ms |
Style & Layout | 420 ms |
Other | 386 ms |
Script Evaluation | 31 ms |
Parse HTML & CSS | 15 ms |
Script Parsing & Compilation | 3 ms |
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.FCPLCP
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.TBT
Third-Party | Transfer Size | Main-Thread Blocking Time |
|---|---|---|
| Google Fonts | 87 KiB | 0 ms |
…v20/UcC73FwrK….woff2 (fonts.gstatic.com) | 48 KiB | 0 ms |
…v40/nuFiD-vYS….woff2 (fonts.gstatic.com) | 38 KiB | 0 ms |
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more.
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Avoids document.write()
document.write() For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Has a <meta name="viewport"> tag with width or initial-scale
<meta name="viewport"> tag with width or initial-scale A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Avoids unload event listeners
unload event listeners The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Failing Elements |
|---|
Handcrafted with precision. <p class="footer-tagline"> |
CodePsych
Building digital experiences that defy limitations.
About
Services
… <footer class="footer"> |
Navigation
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
Failing Elements |
|---|
Full-Stack Expertise <h4> |
Additional items to manually check (10) Show Hide
Additional items to manually check (10)
Show Hide
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.
Passed audits (18) Show Hide
Passed audits (18)
Show Hide
[aria-*] attributes match their roles
[aria-*] attributes match their roles Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
[aria-hidden="true"] is not present on the document <body>
[aria-hidden="true"] is not present on the document <body> Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.
[aria-*] attributes have valid values
[aria-*] attributes have valid values Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
[aria-*] attributes are valid and not misspelled Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
Image elements have [alt] attributes
[alt] attributes Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5. Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
[aria-hidden="true"] elements do not contain focusable descendents
[aria-hidden="true"] elements do not contain focusable descendents Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Document has a <title> element
<title> element The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
[id] attributes on active, focusable elements are unique
[id] attributes on active, focusable elements are unique All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
<html> element has a [lang] attribute
<html> element has a [lang] attribute If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute
<html> element has a valid value for its [lang] attribute Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
<li> elements and script supporting elements (<script> and <template>). Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
List items (<li>) are contained within <ul> or <ol> parent elements
<li>) are contained within <ul> or <ol> parent elements Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
Not applicable (24) Show Hide
Not applicable (24)
Show Hide
[accesskey] values are unique
[accesskey] values are unique Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
button, link, and menuitem elements have accessible names
button, link, and menuitem elements have accessible names When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA meter elements have accessible names
meter elements have accessible names When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA progressbar elements have accessible names
progressbar elements have accessible names When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
[role]s have all required [aria-*] attributes
[role]s have all required [aria-*] attributes Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
[role] that require children to contain a specific [role] have all required children. Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element
[role]s are contained by their required parent element Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
[role] values are valid
[role] values are valid ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA tooltip elements have accessible names
tooltip elements have accessible names When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA treeitem elements have accessible names
treeitem elements have accessible names When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements. When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements
<dl> elements Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.
<frame> or <iframe> elements have a title
<frame> or <iframe> elements have a title Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<input type="image"> elements have [alt] text
<input type="image"> elements have [alt] text When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
The document does not use <meta http-equiv="refresh">
<meta http-equiv="refresh"> Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
<object> elements have alternate text
<object> elements have alternate text Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more.
No element has a [tabindex] value greater than 0
[tabindex] value greater than 0 A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
<table> element that use the [headers] attribute refer to table cells within the same table. Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe. Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
[lang] attributes have a valid value
[lang] attributes have a valid value Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
<video> elements contain a <track> element with [kind="captions"]
<video> elements contain a <track> element with [kind="captions"] When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Description | Directive | Severity |
|---|---|---|
No CSP found in enforcement mode | High |
Passed audits (13) Show Hide
Passed audits (13)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Avoids front-end JavaScript libraries with known security vulnerabilities
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
No browser errors logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
No issues in the Issues panel in Chrome Devtools
Issues panel in Chrome Devtools Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
Not applicable (2) Show Hide
Not applicable (2)
Show Hide
Fonts with font-display: optional are preloaded
font-display: optional are preloaded Preload `optional` fonts so first-time visitors may use them. Learn more
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more.
Crawling and Indexing
robots.txt is not valid 505 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Line # | Content | Error |
|---|---|---|
1 | <!DOCTYPE html> | Syntax not understood |
2 | <html lang="en"> | Syntax not understood |
3 | <head> | Syntax not understood |
4 | <meta charset="UTF-8"> | Syntax not understood |
5 | <meta name="viewport" content="width=device-width, initial-scale=1.0"> | Syntax not understood |
6 | <meta name="description" content="CodePsych - Full-stack web development specializing in custom ecommerce solutions. Custom web development and ecommerce solutions for businesses of ALL types. Custom stores, alternative payments, and bulletproof hosting."> | Syntax not understood |
7 | <meta name="keywords" content="web development, ecommerce, custom websites, shopify alternative, independent business"> | Syntax not understood |
9 | <!-- Open Graph / Social Media --> | Syntax not understood |
10 | <meta property="og:type" content="website"> | Unknown directive |
11 | <meta property="og:title" content="CodePsych | Custom Ecommerce Development"> | Unknown directive |
12 | <meta property="og:description" content="Custom websites, ecommerce stores, and full-stack applications built to fit your business. Custom ecommerce, alternative payments, and full-stack solutions."> | Unknown directive |
13 | <meta property="og:image" content="images/logo-black.png"> | Unknown directive |
14 | <meta name="twitter:card" content="summary_large_image"> | Unknown directive |
16 | <title>CodePsych | Custom Ecommerce Development</title> | Syntax not understood |
17 | <link rel="preconnect" href="https://fonts.googleapis.com"> | Unknown directive |
18 | <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> | Unknown directive |
19 | <link href="https://fonts.googleapis.com/css2?family=Playfair+Display:wght@400;500;600;700&family=Inter:wght@300;400;500;600&display=swap" rel="stylesheet"> | Unknown directive |
20 | <link rel="stylesheet" href="css/style.css"> | Syntax not understood |
21 | <link rel="icon" type="image/png" href="images/logo-tp.png"> | Syntax not understood |
22 | </head> | Syntax not understood |
23 | <body> | Syntax not understood |
24 | <!-- Cursor glow effect --> | Syntax not understood |
25 | <div class="cursor-glow" id="cursorGlow"></div> | Syntax not understood |
27 | <!-- Navigation --> | Syntax not understood |
28 | <nav class="nav" id="nav"> | Syntax not understood |
29 | <div class="nav-container"> | Syntax not understood |
30 | <a href="#" class="logo"> | Syntax not understood |
31 | <img src="images/logo-tp.png" alt="CodePsych" class="logo-img"> | Syntax not understood |
32 | <span class="logo-text">CodePsych</span> | Syntax not understood |
33 | </a> | Syntax not understood |
34 | <div class="nav-links" id="navLinks"> | Syntax not understood |
35 | <a href="#about" class="nav-link">About</a> | Syntax not understood |
36 | <a href="#services" class="nav-link">Services</a> | Syntax not understood |
37 | <a href="#work" class="nav-link">Work</a> | Syntax not understood |
38 | <a href="#process" class="nav-link">Process</a> | Syntax not understood |
39 | <a href="#contact" class="nav-link cta-link">Let's Talk</a> | Syntax not understood |
40 | </div> | Syntax not understood |
41 | <button class="nav-toggle" id="navToggle" aria-label="Toggle menu"> | Syntax not understood |
42 | <span></span> | Syntax not understood |
43 | <span></span> | Syntax not understood |
44 | <span></span> | Syntax not understood |
45 | </button> | Syntax not understood |
46 | </div> | Syntax not understood |
47 | </nav> | Syntax not understood |
49 | <!-- Hero Section --> | Syntax not understood |
50 | <header class="hero"> | Syntax not understood |
51 | <div class="hero-bg"> | Syntax not understood |
52 | <div class="grid-overlay"></div> | Syntax not understood |
53 | <div class="gradient-orb orb-1"></div> | Syntax not understood |
54 | <div class="gradient-orb orb-2"></div> | Syntax not understood |
55 | <img src="images/logo-tp.png" alt="" class="hero-logo-bg" aria-hidden="true"> | Syntax not understood |
56 | </div> | Syntax not understood |
57 | <div class="hero-content"> | Syntax not understood |
58 | <div class="hero-badge"> | Syntax not understood |
59 | <span class="badge-dot"></span> | Syntax not understood |
60 | Available for new projects | Syntax not understood |
61 | </div> | Syntax not understood |
62 | <h1 class="hero-title"> | Syntax not understood |
63 | <span class="title-line">Where Code</span> | Syntax not understood |
64 | <span class="title-line title-accent">Meets Strategy</span> | Syntax not understood |
65 | </h1> | Syntax not understood |
66 | <p class="hero-subtitle"> | Syntax not understood |
67 | Full-stack development for businesses ready to stand out online. Custom websites, powerful ecommerce, and applications built exactly to your needs. | Syntax not understood |
68 | </p> | Syntax not understood |
69 | <div class="hero-actions"> | Syntax not understood |
70 | <a href="#contact" class="btn btn-primary"> | Syntax not understood |
71 | <span>Start Your Project</span> | Syntax not understood |
72 | <svg width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"> | Syntax not understood |
73 | <path d="M5 12h14M12 5l7 7-7 7"/> | Syntax not understood |
74 | </svg> | Syntax not understood |
75 | </a> | Syntax not understood |
76 | <a href="#work" class="btn btn-secondary">View Work</a> | Syntax not understood |
77 | </div> | Syntax not understood |
78 | <div class="hero-stats"> | Syntax not understood |
79 | <div class="stat"> | Syntax not understood |
80 | <span class="stat-number" data-count="50">0</span> | Syntax not understood |
81 | <span class="stat-suffix">+</span> | Syntax not understood |
82 | <span class="stat-label">Projects Delivered</span> | Syntax not understood |
83 | </div> | Syntax not understood |
84 | <div class="stat-divider"></div> | Syntax not understood |
85 | <div class="stat"> | Syntax not understood |
86 | <span class="stat-number" data-count="100">0</span> | Syntax not understood |
87 | <span class="stat-suffix">%</span> | Syntax not understood |
88 | <span class="stat-label">Client Satisfaction</span> | Syntax not understood |
89 | </div> | Syntax not understood |
90 | <div class="stat-divider"></div> | Syntax not understood |
91 | <div class="stat"> | Syntax not understood |
92 | <span class="stat-number" data-count="24">0</span> | Syntax not understood |
93 | <span class="stat-suffix">/7</span> | Syntax not understood |
94 | <span class="stat-label">Dedicated Support</span> | Syntax not understood |
95 | </div> | Syntax not understood |
96 | </div> | Syntax not understood |
97 | </div> | Syntax not understood |
98 | <div class="scroll-indicator"> | Syntax not understood |
99 | <span>Scroll</span> | Syntax not understood |
100 | <div class="scroll-line"></div> | Syntax not understood |
101 | </div> | Syntax not understood |
102 | </header> | Syntax not understood |
104 | <!-- About Section --> | Syntax not understood |
105 | <section class="section about" id="about"> | Syntax not understood |
106 | <div class="container"> | Syntax not understood |
107 | <div class="section-grid"> | Syntax not understood |
108 | <div class="section-header"> | Syntax not understood |
109 | <span class="section-tag">About</span> | Syntax not understood |
110 | <h2 class="section-title">The Developer Behind<br><span class="gold">CodePsych</span></h2> | Syntax not understood |
111 | </div> | Syntax not understood |
112 | <div class="section-content"> | Syntax not understood |
113 | <p class="lead-text"> | Syntax not understood |
114 | I believe every business deserves a powerful online presence, tailored to their style and needs. | Syntax not understood |
115 | </p> | Syntax not understood |
116 | <p> | Syntax not understood |
117 | Too many entrepreneurs settle for cookie-cutter platforms that limit their potential. I'm here for businesses that need more than just a platform, they need a partner. | Syntax not understood |
118 | </p> | Syntax not understood |
119 | <p> | Syntax not understood |
120 | From alternative payment options to bulletproof hosting solutions, I build ecommerce experiences as unique as your products. Can't get approved by traditional processors? I create intuitive checkout flows that keep your business running. Every site includes a fully integrated admin suite, no third-party dashboards, no extra subscriptions, no arbitrary restrictions, no sudden account terminations. Just solid code and genuine support. | Syntax not understood |
121 | </p> | Syntax not understood |
122 | <div class="about-features"> | Syntax not understood |
123 | <div class="feature"> | Syntax not understood |
124 | <div class="feature-icon"> | Syntax not understood |
125 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
126 | <path d="M12 2L2 7l10 5 10-5-10-5zM2 17l10 5 10-5M2 12l10 5 10-5"/> | Syntax not understood |
127 | </svg> | Syntax not understood |
128 | </div> | Syntax not understood |
129 | <div class="feature-text"> | Syntax not understood |
130 | <h4>Full-Stack Expertise</h4> | Syntax not understood |
131 | <p>Frontend to backend, I handle every layer</p> | Syntax not understood |
132 | </div> | Syntax not understood |
133 | </div> | Syntax not understood |
134 | <div class="feature"> | Syntax not understood |
135 | <div class="feature-icon"> | Syntax not understood |
136 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
137 | <path d="M12 22s8-4 8-10V5l-8-3-8 3v7c0 6 8 10 8 10z"/> | Syntax not understood |
138 | </svg> | Syntax not understood |
139 | </div> | Syntax not understood |
140 | <div class="feature-text"> | Syntax not understood |
141 | <h4>No Platform Risk</h4> | Syntax not understood |
142 | <p>Your site, your rules, your control</p> | Syntax not understood |
143 | </div> | Syntax not understood |
144 | </div> | Syntax not understood |
145 | <div class="feature"> | Syntax not understood |
146 | <div class="feature-icon"> | Syntax not understood |
147 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
148 | <circle cx="12" cy="12" r="10"/> | Syntax not understood |
149 | <path d="M12 6v6l4 2"/> | Syntax not understood |
150 | </svg> | Syntax not understood |
151 | </div> | Syntax not understood |
152 | <div class="feature-text"> | Syntax not understood |
153 | <h4>Mobile-First Design</h4> | Syntax not understood |
154 | <p>Every site works flawlessly on any device</p> | Syntax not understood |
155 | </div> | Syntax not understood |
156 | </div> | Syntax not understood |
157 | </div> | Syntax not understood |
158 | </div> | Syntax not understood |
159 | </div> | Syntax not understood |
160 | </div> | Syntax not understood |
161 | </section> | Syntax not understood |
163 | <!-- Services Section --> | Syntax not understood |
164 | <section class="section services" id="services"> | Syntax not understood |
165 | <div class="container"> | Syntax not understood |
166 | <div class="section-header centered"> | Syntax not understood |
167 | <span class="section-tag">Services</span> | Syntax not understood |
168 | <h2 class="section-title">What I <span class="gold">Build</span></h2> | Syntax not understood |
169 | <p class="section-subtitle">End-to-end solutions tailored to your business</p> | Syntax not understood |
170 | </div> | Syntax not understood |
171 | <div class="services-grid"> | Syntax not understood |
172 | <article class="service-card"> | Syntax not understood |
173 | <div class="service-number">01</div> | Syntax not understood |
174 | <div class="service-icon"> | Syntax not understood |
175 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
176 | <rect x="2" y="3" width="20" height="14" rx="2"/> | Syntax not understood |
177 | <path d="M8 21h8M12 17v4"/> | Syntax not understood |
178 | </svg> | Syntax not understood |
179 | </div> | Syntax not understood |
180 | <h3 class="service-title">Custom Ecommerce</h3> | Syntax not understood |
181 | <p class="service-desc">Bespoke online stores built from the ground up with fully integrated admin suites. Fully mobile-responsive—manage everything from one place, no third-party dashboards required.</p> | Syntax not understood |
182 | <ul class="service-features"> | Syntax not understood |
183 | <li>Integrated admin dashboard & analytics</li> | Syntax not understood |
184 | <li>Product & inventory management</li> | Syntax not understood |
185 | <li>Customer accounts & order tracking</li> | Syntax not understood |
186 | <li>Email automation integration</li> | Syntax not understood |
187 | </ul> | Syntax not understood |
188 | </article> | Syntax not understood |
189 | <article class="service-card featured"> | Syntax not understood |
190 | <div class="featured-badge">Most Popular</div> | Syntax not understood |
191 | <div class="service-number">02</div> | Syntax not understood |
192 | <div class="service-icon"> | Syntax not understood |
193 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
194 | <rect x="1" y="4" width="22" height="16" rx="2"/> | Syntax not understood |
195 | <path d="M1 10h22"/> | Syntax not understood |
196 | </svg> | Syntax not understood |
197 | </div> | Syntax not understood |
198 | <h3 class="service-title">Payment Solutions</h3> | Syntax not understood |
199 | <p class="service-desc">Flexible payment integration for any business model. From standard processors to alternative methods, I build checkout flows that keep customers paying and your business thriving.</p> | Syntax not understood |
200 | <ul class="service-features"> | Syntax not understood |
201 | <li>Alternative payment methods for ANY business</li> | Syntax not understood |
202 | <li>Cryptocurrency integration</li> | Syntax not understood |
203 | <li>Intuitive checkout experiences</li> | Syntax not understood |
204 | <li>Multiple fallback options</li> | Syntax not understood |
205 | </ul> | Syntax not understood |
206 | </article> | Syntax not understood |
207 | <article class="service-card"> | Syntax not understood |
208 | <div class="service-number">03</div> | Syntax not understood |
209 | <div class="service-icon"> | Syntax not understood |
210 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
211 | <path d="M12 2L2 7l10 5 10-5-10-5z"/> | Syntax not understood |
212 | <path d="M2 17l10 5 10-5"/> | Syntax not understood |
213 | <path d="M2 12l10 5 10-5"/> | Syntax not understood |
214 | </svg> | Syntax not understood |
215 | </div> | Syntax not understood |
216 | <h3 class="service-title">Full-Stack Apps</h3> | Syntax not understood |
217 | <p class="service-desc">Complete web applications with robust backends and seamlessly integrated admin panels. Everything lives on your site—one login, total control.</p> | Syntax not understood |
218 | <ul class="service-features"> | Syntax not understood |
219 | <li>Custom admin suites built into your site</li> | Syntax not understood |
220 | <li>RESTful API development</li> | Syntax not understood |
221 | <li>Database design & optimization</li> | Syntax not understood |
222 | <li>Real-time analytics dashboards</li> | Syntax not understood |
223 | </ul> | Syntax not understood |
224 | </article> | Syntax not understood |
225 | <article class="service-card"> | Syntax not understood |
226 | <div class="service-number">04</div> | Syntax not understood |
227 | <div class="service-icon"> | Syntax not understood |
228 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
229 | <path d="M14.7 6.3a1 1 0 000 1.4l1.6 1.6a1 1 0 001.4 0l3.77-3.77a6 6 0 01-7.94 7.94l-6.91 6.91a2.12 2.12 0 01-3-3l6.91-6.91a6 6 0 017.94-7.94l-3.76 3.76z"/> | Syntax not understood |
230 | </svg> | Syntax not understood |
231 | </div> | Syntax not understood |
232 | <h3 class="service-title">Migration & Rescue</h3> | Syntax not understood |
233 | <p class="service-desc">Seamless migration from Shopify, WooCommerce, or any platform. Lost your store? I'll help you rebuild, better.</p> | Syntax not understood |
234 | <ul class="service-features"> | Syntax not understood |
235 | <li>Data migration & preservation</li> | Syntax not understood |
236 | <li>SEO preservation strategies</li> | Syntax not understood |
237 | <li>Improved performance & speed</li> | Syntax not understood |
238 | <li>Enhanced security measures</li> | Syntax not understood |
239 | </ul> | Syntax not understood |
240 | </article> | Syntax not understood |
241 | <article class="service-card"> | Syntax not understood |
242 | <div class="service-number">05</div> | Syntax not understood |
243 | <div class="service-icon"> | Syntax not understood |
244 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
245 | <polygon points="12 2 15.09 8.26 22 9.27 17 14.14 18.18 21.02 12 17.77 5.82 21.02 7 14.14 2 9.27 8.91 8.26 12 2"/> | Syntax not understood |
246 | </svg> | Syntax not understood |
247 | </div> | Syntax not understood |
248 | <h3 class="service-title">Logo Design & Remaster</h3> | Syntax not understood |
249 | <p class="service-desc">Your brand deserves an identity that stands out. Fresh logo design or breathe new life into your existing mark with a professional remaster.</p> | Syntax not understood |
250 | <ul class="service-features"> | Syntax not understood |
251 | <li>Custom logo design from scratch</li> | Syntax not understood |
252 | <li>Logo remastering & modernization</li> | Syntax not understood |
253 | <li>Multiple format deliverables</li> | Syntax not understood |
254 | <li>Brand consistency across your site</li> | Syntax not understood |
255 | </ul> | Syntax not understood |
256 | </article> | Syntax not understood |
257 | <article class="service-card"> | Syntax not understood |
258 | <div class="service-number">06</div> | Syntax not understood |
259 | <div class="service-icon"> | Syntax not understood |
260 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
261 | <path d="M4 4h16c1.1 0 2 .9 2 2v12c0 1.1-.9 2-2 2H4c-1.1 0-2-.9-2-2V6c0-1.1.9-2 2-2z"/> | Syntax not understood |
262 | <polyline points="22,6 12,13 2,6"/> | Syntax not understood |
263 | </svg> | Syntax not understood |
264 | </div> | Syntax not understood |
265 | <h3 class="service-title">Business Email Setup</h3> | Syntax not understood |
266 | <p class="service-desc">Professional email addresses that match your domain. Look legitimate from the first message you send.</p> | Syntax not understood |
267 | <ul class="service-features"> | Syntax not understood |
268 | <li>Custom domain email addresses</li> | Syntax not understood |
269 | <li>Email hosting configuration</li> | Syntax not understood |
270 | <li>Multiple mailboxes & aliases</li> | Syntax not understood |
271 | <li>Seamless integration with your workflow</li> | Syntax not understood |
272 | </ul> | Syntax not understood |
273 | </article> | Syntax not understood |
274 | </div> | Syntax not understood |
275 | </div> | Syntax not understood |
276 | </section> | Syntax not understood |
278 | <!-- Work/Portfolio Section --> | Syntax not understood |
279 | <section class="section work" id="work"> | Syntax not understood |
280 | <div class="container"> | Syntax not understood |
281 | <div class="section-header"> | Syntax not understood |
282 | <span class="section-tag">Portfolio</span> | Syntax not understood |
283 | <h2 class="section-title">Selected <span class="gold">Work</span></h2> | Syntax not understood |
284 | <p class="section-subtitle">Real solutions built for real businesses</p> | Syntax not understood |
285 | </div> | Syntax not understood |
286 | <div class="work-showcase"> | Syntax not understood |
287 | <div class="showcase-preview showcase-preview-prev" id="previewPrev"> | Syntax not understood |
288 | <img src="images/customer-profile.png" alt="Previous"> | Syntax not understood |
289 | </div> | Syntax not understood |
290 | <button class="showcase-nav showcase-prev" aria-label="Previous image"> | Syntax not understood |
291 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"> | Syntax not understood |
292 | <path d="M15 18l-6-6 6-6"/> | Syntax not understood |
293 | </svg> | Syntax not understood |
294 | </button> | Syntax not understood |
295 | <div class="showcase-main"> | Syntax not understood |
296 | <div class="showcase-image-wrapper" id="showcaseWrapper"> | Syntax not understood |
297 | <img src="images/home1.png" alt="Custom ecommerce homepage design" id="showcaseImage"> | Syntax not understood |
298 | <div class="showcase-expand-hint"> | Syntax not understood |
299 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"> | Syntax not understood |
300 | <path d="M15 3h6v6M9 21H3v-6M21 3l-7 7M3 21l7-7"/> | Syntax not understood |
301 | </svg> | Syntax not understood |
302 | <span>Click to expand</span> | Syntax not understood |
303 | </div> | Syntax not understood |
304 | </div> | Syntax not understood |
305 | <div class="showcase-info"> | Syntax not understood |
306 | <span class="work-category" id="showcaseCategory">Homepage Design</span> | Syntax not understood |
307 | <h3 class="work-title" id="showcaseTitle">Custom Storefront</h3> | Syntax not understood |
308 | </div> | Syntax not understood |
309 | </div> | Syntax not understood |
310 | <button class="showcase-nav showcase-next" aria-label="Next image"> | Syntax not understood |
311 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"> | Syntax not understood |
312 | <path d="M9 18l6-6-6-6"/> | Syntax not understood |
313 | </svg> | Syntax not understood |
314 | </button> | Syntax not understood |
315 | <div class="showcase-preview showcase-preview-next" id="previewNext"> | Syntax not understood |
316 | <img src="images/home2.png" alt="Next"> | Syntax not understood |
317 | </div> | Syntax not understood |
318 | </div> | Syntax not understood |
319 | <div class="showcase-dots" id="showcaseDots"></div> | Syntax not understood |
321 | <!-- Lightbox for full-size image --> | Syntax not understood |
322 | <div class="lightbox" id="lightbox"> | Syntax not understood |
323 | <button class="lightbox-close" aria-label="Close"> | Syntax not understood |
324 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"> | Syntax not understood |
325 | <path d="M18 6L6 18M6 6l12 12"/> | Syntax not understood |
326 | </svg> | Syntax not understood |
327 | </button> | Syntax not understood |
328 | <button class="lightbox-nav lightbox-prev" aria-label="Previous"> | Syntax not understood |
329 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"> | Syntax not understood |
330 | <path d="M15 18l-6-6 6-6"/> | Syntax not understood |
331 | </svg> | Syntax not understood |
332 | </button> | Syntax not understood |
333 | <div class="lightbox-content"> | Syntax not understood |
334 | <img src="images/home1.png" alt="Portfolio preview" id="lightboxImage"> | Syntax not understood |
335 | <div class="lightbox-info"> | Syntax not understood |
336 | <span class="lightbox-category" id="lightboxCategory"></span> | Syntax not understood |
337 | <h3 class="lightbox-title" id="lightboxTitle"><span class="sr-only">Image title</span></h3> | Syntax not understood |
338 | </div> | Syntax not understood |
339 | </div> | Syntax not understood |
340 | <button class="lightbox-nav lightbox-next" aria-label="Next"> | Syntax not understood |
341 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"> | Syntax not understood |
342 | <path d="M9 18l6-6-6-6"/> | Syntax not understood |
343 | </svg> | Syntax not understood |
344 | </button> | Syntax not understood |
345 | </div> | Syntax not understood |
346 | </div> | Syntax not understood |
347 | </section> | Syntax not understood |
349 | <!-- Process Section --> | Syntax not understood |
350 | <section class="section process" id="process"> | Syntax not understood |
351 | <div class="container"> | Syntax not understood |
352 | <div class="section-header centered"> | Syntax not understood |
353 | <span class="section-tag">Process</span> | Syntax not understood |
354 | <h2 class="section-title">How We <span class="gold">Work Together</span></h2> | Syntax not understood |
355 | <p class="section-subtitle">A collaborative approach to bringing your vision to life</p> | Syntax not understood |
356 | </div> | Syntax not understood |
357 | <div class="process-timeline"> | Syntax not understood |
358 | <div class="process-step"> | Syntax not understood |
359 | <div class="step-marker"> | Syntax not understood |
360 | <span class="step-number">01</span> | Syntax not understood |
361 | <div class="step-line"></div> | Syntax not understood |
362 | </div> | Syntax not understood |
363 | <div class="step-content"> | Syntax not understood |
364 | <h3>Discovery Call</h3> | Syntax not understood |
365 | <p>We discuss your business, goals, and specific needs. I'll learn what makes your brand unique and what obstacles you've faced with other platforms.</p> | Syntax not understood |
366 | </div> | Syntax not understood |
367 | </div> | Syntax not understood |
368 | <div class="process-step"> | Syntax not understood |
369 | <div class="step-marker"> | Syntax not understood |
370 | <span class="step-number">02</span> | Syntax not understood |
371 | <div class="step-line"></div> | Syntax not understood |
372 | </div> | Syntax not understood |
373 | <div class="step-content"> | Syntax not understood |
374 | <h3>Strategy & Proposal</h3> | Syntax not understood |
375 | <p>I craft a detailed plan outlining the technical approach, timeline, and investment. You have full control over the features and design—no surprises, just clear expectations.</p> | Syntax not understood |
376 | </div> | Syntax not understood |
377 | </div> | Syntax not understood |
378 | <div class="process-step"> | Syntax not understood |
379 | <div class="step-marker"> | Syntax not understood |
380 | <span class="step-number">03</span> | Syntax not understood |
381 | <div class="step-line"></div> | Syntax not understood |
382 | </div> | Syntax not understood |
383 | <div class="step-content"> | Syntax not understood |
384 | <h3>Design & Development</h3> | Syntax not understood |
385 | <p>Your vision takes shape. We work hand in hand with regular check-ins, keeping you in the loop as your custom platform comes to life, piece by piece.</p> | Syntax not understood |
386 | </div> | Syntax not understood |
387 | </div> | Syntax not understood |
388 | <div class="process-step"> | Syntax not understood |
389 | <div class="step-marker"> | Syntax not understood |
390 | <span class="step-number">04</span> | Syntax not understood |
391 | <div class="step-line"></div> | Syntax not understood |
392 | </div> | Syntax not understood |
393 | <div class="step-content"> | Syntax not understood |
394 | <h3>Launch & Beyond</h3> | Syntax not understood |
395 | <p>We go live with thorough testing and smooth deployment. Post-launch support ensures your store runs flawlessly as you scale.</p> | Syntax not understood |
396 | </div> | Syntax not understood |
397 | </div> | Syntax not understood |
398 | </div> | Syntax not understood |
399 | </div> | Syntax not understood |
400 | </section> | Syntax not understood |
402 | <!-- Testimonial/Trust Section --> | Syntax not understood |
403 | <section class="section trust"> | Syntax not understood |
404 | <div class="container"> | Syntax not understood |
405 | <div class="trust-content"> | Syntax not understood |
406 | <blockquote class="trust-quote"> | Syntax not understood |
407 | <svg class="quote-mark" viewBox="0 0 24 24" fill="currentColor"> | Syntax not understood |
408 | <path d="M11.192 15.757c0-.88-.23-1.618-.69-2.217-.326-.412-.768-.683-1.327-.812-.55-.128-1.07-.137-1.54-.028-.16-.95.1-1.956.76-3.022.66-1.065 1.515-1.867 2.558-2.403L9.373 5c-.8.396-1.56.898-2.26 1.505-.71.607-1.34 1.305-1.9 2.094s-.98 1.68-1.25 2.69-.346 2.04-.217 3.1c.168 1.4.62 2.52 1.356 3.35.735.84 1.652 1.26 2.748 1.26.965 0 1.766-.29 2.4-.878.628-.576.94-1.365.94-2.368l.002.003zm9.124 0c0-.88-.23-1.618-.69-2.217-.326-.42-.77-.692-1.327-.817-.56-.124-1.074-.13-1.54-.022-.16-.94.09-1.95.75-3.02.66-1.06 1.514-1.86 2.557-2.4L18.49 5c-.8.396-1.555.898-2.26 1.505-.708.607-1.34 1.305-1.894 2.094-.556.79-.97 1.68-1.24 2.69-.273 1-.345 2.04-.217 3.1.168 1.4.62 2.52 1.356 3.35.735.84 1.652 1.26 2.748 1.26.965 0 1.766-.29 2.4-.878.628-.576.94-1.365.94-2.368l-.007.006z"/> | Syntax not understood |
409 | </svg> | Syntax not understood |
410 | <p>Every merchant deserves the tools to succeed online. I build them.</p> | Syntax not understood |
411 | </blockquote> | Syntax not understood |
412 | </div> | Syntax not understood |
413 | </div> | Syntax not understood |
414 | </section> | Syntax not understood |
416 | <!-- Contact Section --> | Syntax not understood |
417 | <section class="section contact" id="contact"> | Syntax not understood |
418 | <img src="images/logo-tp.png" alt="" class="section-logo-bg" aria-hidden="true"> | Syntax not understood |
419 | <div class="container"> | Syntax not understood |
420 | <div class="contact-grid"> | Syntax not understood |
421 | <div class="contact-info"> | Syntax not understood |
422 | <span class="section-tag">Contact</span> | Syntax not understood |
423 | <h2 class="section-title">Let's Build<br><span class="gold">Something Great</span></h2> | Syntax not understood |
424 | <p class="contact-desc"> | Syntax not understood |
425 | Ready to take control of your online presence? Whether you're starting fresh, escaping platform limitations, or need creative payment solutions, I'm here to help. | Syntax not understood |
426 | </p> | Syntax not understood |
427 | <div class="contact-details"> | Syntax not understood |
428 | <a href="mailto:codepsych@pm.me" class="contact-link"> | Unknown directive |
429 | <div class="contact-icon"> | Syntax not understood |
430 | <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"> | Syntax not understood |
431 | <path d="M4 4h16c1.1 0 2 .9 2 2v12c0 1.1-.9 2-2 2H4c-1.1 0-2-.9-2-2V6c0-1.1.9-2 2-2z"/> | Syntax not understood |
432 | <polyline points="22,6 12,13 2,6"/> | Syntax not understood |
433 | </svg> | Syntax not understood |
434 | </div> | Syntax not understood |
435 | <div class="contact-text"> | Syntax not understood |
436 | <span class="contact-label">Email</span> | Syntax not understood |
437 | <span class="contact-value">codepsych@pm.me</span> | Syntax not understood |
438 | </div> | Syntax not understood |
439 | </a> | Syntax not understood |
440 | </div> | Syntax not understood |
441 | <div class="contact-availability"> | Syntax not understood |
442 | <div class="availability-indicator"> | Syntax not understood |
443 | <span class="pulse"></span> | Syntax not understood |
444 | <span>Currently accepting new projects</span> | Syntax not understood |
445 | </div> | Syntax not understood |
446 | </div> | Syntax not understood |
447 | </div> | Syntax not understood |
448 | <div class="contact-form-wrapper"> | Syntax not understood |
449 | <form action='/' class='contact-form' id='contactForm' method='POST' name='contact'> | Syntax not understood |
450 | <input type="hidden" name="form-name" value="contact"> | Syntax not understood |
451 | <p class="honeypot"> | Syntax not understood |
452 | <label>Don't fill this out if you're human: <input name="bot-field"></label> | Unknown directive |
453 | </p> | Syntax not understood |
454 | <div class="form-group"> | Syntax not understood |
455 | <label for="name">Name</label> | Syntax not understood |
456 | <input type="text" id="name" name="name" required placeholder="Your name"> | Syntax not understood |
457 | </div> | Syntax not understood |
458 | <div class="form-group"> | Syntax not understood |
459 | <label for="email">Email</label> | Syntax not understood |
460 | <input type="email" id="email" name="email" required placeholder="your@email.com"> | Syntax not understood |
461 | </div> | Syntax not understood |
462 | <div class="form-group"> | Syntax not understood |
463 | <label for="project">Project Type</label> | Syntax not understood |
464 | <select id="project" name="project" required> | Syntax not understood |
465 | <option value="" disabled selected>Select a service</option> | Syntax not understood |
466 | <option value="ecommerce">Custom Ecommerce Store</option> | Syntax not understood |
467 | <option value="payments">Payment Integration</option> | Syntax not understood |
468 | <option value="webapp">Full-Stack Application</option> | Syntax not understood |
469 | <option value="migration">Platform Migration</option> | Syntax not understood |
470 | <option value="logo">Logo Design & Remaster</option> | Syntax not understood |
471 | <option value="email">Business Email Setup</option> | Syntax not understood |
472 | <option value="other">Something Else</option> | Syntax not understood |
473 | </select> | Syntax not understood |
474 | </div> | Syntax not understood |
475 | <div class="form-group"> | Syntax not understood |
476 | <label for="message">Tell me about your project</label> | Syntax not understood |
477 | <textarea id="message" name="message" rows="4" required placeholder="What are you looking to build? What challenges have you faced?"></textarea> | Syntax not understood |
478 | </div> | Syntax not understood |
479 | <button type="submit" class="btn btn-primary btn-full"> | Syntax not understood |
480 | <span>Send Message</span> | Syntax not understood |
481 | <svg width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"> | Syntax not understood |
482 | <path d="M22 2L11 13M22 2l-7 20-4-9-9-4 20-7z"/> | Syntax not understood |
483 | </svg> | Syntax not understood |
484 | </button> | Syntax not understood |
485 | </form> | Syntax not understood |
486 | </div> | Syntax not understood |
487 | </div> | Syntax not understood |
488 | </div> | Syntax not understood |
489 | </section> | Syntax not understood |
491 | <!-- Footer --> | Syntax not understood |
492 | <footer class="footer"> | Syntax not understood |
493 | <div class="container"> | Syntax not understood |
494 | <div class="footer-content"> | Syntax not understood |
495 | <div class="footer-brand"> | Syntax not understood |
496 | <a href="#" class="logo"> | Syntax not understood |
497 | <img src="images/logo-tp.png" alt="CodePsych" class="logo-img"> | Syntax not understood |
498 | <span class="logo-text">CodePsych</span> | Syntax not understood |
499 | </a> | Syntax not understood |
500 | <p>Building digital experiences that defy limitations.</p> | Syntax not understood |
501 | </div> | Syntax not understood |
502 | <div class="footer-links"> | Syntax not understood |
503 | <a href="#about">About</a> | Syntax not understood |
504 | <a href="#services">Services</a> | Syntax not understood |
505 | <a href="#work">Work</a> | Syntax not understood |
506 | <a href="#contact">Contact</a> | Syntax not understood |
507 | </div> | Syntax not understood |
508 | <div class="footer-bottom"> | Syntax not understood |
509 | <p>© 2025 CodePsych. All rights reserved.</p> | Syntax not understood |
510 | <p class="footer-tagline">Handcrafted with precision.</p> | Syntax not understood |
511 | </div> | Syntax not understood |
512 | </div> | Syntax not understood |
513 | </div> | Syntax not understood |
514 | </footer> | Syntax not understood |
516 | <script src="js/main.js"></script> | Syntax not understood |
517 | </body> | Syntax not understood |
518 | </html> | Syntax not understood |
Additional items to manually check (1) Show Hide
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Passed audits (11) Show Hide
Passed audits (11)
Show Hide
Has a <meta name="viewport"> tag with width or initial-scale
<meta name="viewport"> tag with width or initial-scale A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Document has a <title> element
<title> element The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn more.
Links are crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Image elements have [alt] attributes
[alt] attributes Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document has a valid hreflang
hreflang hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Document uses legible font sizes 99.9% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.
Source | Selector | % of Page Text | Font Size |
|---|---|---|---|
/css/style.css:734:17 (69c14b8d695f25143572f5b8--codepsych.netlify.app) | .featured-badge | 0.07% | 11px |
/css/style.css:505:19 (69c14b8d695f25143572f5b8--codepsych.netlify.app) | .scroll-indicator | 0.03% | 11px |
Legible text | 99.90% | ≥ 12px |
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Not applicable (1) Show Hide
Not applicable (1)
Show Hide
Document has a valid rel=canonical
rel=canonical Canonical links suggest which URL to show in search results. Learn more.
These checks validate the aspects of a Progressive Web App. Learn more.
Installable
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Failure reason |
|---|
No manifest was fetched |
PWA Optimized
Does not register a service worker that controls page and start_url
start_url The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Is not configured for a custom splash screenFailures: No manifest was fetched.
Failures: No manifest was fetched.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.
Does not set a theme color for the address bar.Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
The browser address bar can be themed to match your site. Learn more.
Content is sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
<meta name="viewport"> tag with width or initial-scale A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Does not provide a valid apple-touch-icon
apple-touch-icon For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Manifest doesn't have a maskable iconNo manifest was fetched
No manifest was fetched
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.
Additional items to manually check (3) Show Hide
Additional items to manually check (3)
Show Hide
Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn more.
Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more.
Each page has a URL
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more.