Nibbler SEO audit for phpooey.com

Overall6.5

The overall score for this website.

Accessibility7.8

How accessible the website is to mobile and disabled users.

The following tests contribute to this score:

Experience5.5

How satisfying the website is likely to be for users.

Marketing3.3

How well marketed and popular the website is.

Technology7.0

How well designed and built the website is.

Nibbler tested a sample of 5 pages from this website at 6:18 PM on Apr 28, 2024 (BST).

Top priorities for website improvement

  • Check how the website looks using a mobile and a tablet. Consider adding mobile-only styling using media queries. Some websites employ other techniques for mobile visitors which we cannot currently detect. (read more)
  • Consider a leading website analytics solution, such as WebTrends or Google Analytics. (read more)
  • Make sure that all the pages of this website include a meta description. If you don't include one, Google will choose a sample of text from the page to appear in the search engine result. By including a meta description, you can control how your search engine result will appear. (read more)

Twitter0.0

This website does not appear to be associated with a Twitter account.

  • This website did not contain a link to Twitter.
    • Sign up for a Twitter account and make sure it is linked to from your site.

Analytics0.0

0% of pages use analytics

No Analytics SolutionNo

  • None of this website is using any recognised analytics software. It is still possible to gather a great deal of information from webserver logs, however complete visitor analysis requires client-side Javascript or an image not found here.
    • Consider a leading website analytics solution, such as WebTrends or Google Analytics.
  • Note that this test can only detect recognised analytics solutions. If an analytics solution is new, obscure or used in a non-standard way (e.g. it has been customised) it may not be detected.

Printability0.0

0% of pages are optimized for printing

Meta tags2.0

Meta Tags (http-equiv attribute)

Page URLNameContent
phpooey.com/Content-Typetext/html; charset=utf-8
www.phpooey.com/index.phpContent-Typetext/html; charset=utf-8
www.phpooey.com/index.php/.../Content-Typetext/html; charset=utf-8
www.phpooey.com/index.php/.../Content-Typetext/html; charset=utf-8
www.phpooey.com/index.php/.../Content-Typetext/html; charset=utf-8

Mobile3.0

Mobile screenshot of phpooey.comTablet screenshot of phpooey.com
  • None of this website appears to be optimized for viewing on a mobile or tablet (using CSS media queries). It is important to make sure your content is optimized for a wide range of devices as a growing percentage of web browsing is done on phones and tablets.

Media specific CSS detected

Amount of content5.4

Rendering Chart...

  • This website has an average of 69 words per page. The amount of content on a website has been shown to correlate with its search engine ranking.
    • Consider the amount of text on this website and increase it if appropriate.

Server behavior6.6

Yes404 page

YesCompression

Headings7.7

archives categories developer entries feed monthly most musings phpooey recent search syndicate twitter

  • All pages were found to use defined headings. This is excellent as it allows visitors and search engines to summarize the content of webpages quickly. Correctly defined headings aid accessibility and are particularly important for search engine optimization.
  • Many headings (6.0%) were found to be empty, or incorrectly defined. Empty or invalid headings are of no value to search engines and make a website less accessible.
    • Make sure all headings have content which is relevant to the page of content.
  • Some pages did not define headings correctly. The H1 tag should be used for the most top-level heading, with H2 being used for sub-headings and H3 for further sub-headings and so-on. Not conforming to this convention may confuse visitors.
    • Ensure that headings are defined in a semantically correct way, i.e. always start with a H1 tag. This is used to summarise the page content. Further tags (H2, H3, H4 etc) are meant to summarise and partition sections within the content.

Page headings detail

URLHeadingLevel
phpooey.com/PHPooey - Musings of a php developerH1
phpooey.com/Twitter FeedH2
phpooey.com/SearchH2
phpooey.com/CategoriesH2
phpooey.com/Monthly ArchivesH2
phpooey.com/Most recent entriesH2
phpooey.com/SyndicateH2
www.phpooey.com/index.phpPHPooey - Musings of a php developerH1
www.phpooey.com/index.phpTwitter FeedH2
www.phpooey.com/index.phpSearchH2
www.phpooey.com/index.phpCategoriesH2
www.phpooey.com/index.phpMonthly ArchivesH2
www.phpooey.com/index.phpMost recent entriesH2
www.phpooey.com/index.phpSyndicateH2
www.phpooey.com/index.php/.../AboutH2
www.phpooey.com/index.php/.../Monthly ArchivesH2
www.phpooey.com/index.php/.../Most recent entriesH2
www.phpooey.com/index.php/.../SyndicateH2
www.phpooey.com/index.php/.../AboutH2
www.phpooey.com/index.php/.../Monthly ArchivesH2
www.phpooey.com/index.php/.../Most recent entriesH2
www.phpooey.com/index.php/.../SyndicateH2
www.phpooey.com/index.php/.../PHPooey - Musings of a php developerH1
www.phpooey.com/index.php/.../Twitter FeedH2
www.phpooey.com/index.php/.../SearchH2
www.phpooey.com/index.php/.../CategoriesH2
www.phpooey.com/index.php/.../Monthly ArchivesH2
www.phpooey.com/index.php/.../Most recent entriesH2
www.phpooey.com/index.php/.../SyndicateH2

URL format8.8

  • 1 URLs include a file extension.
    • Avoid use of file extensions wherever possible. File extensions appear at the end of web addresses, and have several negative effects. They make the address harder to remember or type (particularly for non-technical users), and can reveal the underlying technology of the website making it very slightly more vulnerable to hackers. They also tie the implementation of the website to a specific technology, which can make subsequent migration of URLs difficult. Consider URL rewriting as an effective and transparent means of creating appropriate URLs.

      Page extensions

Page titles10.0

100% of pages have defined titles

0% of page titles are weak

  • All pages were found to use page titles appropriately. Page titles appear in search results and at the top of the browser's window when visiting the site. Appropriate page titles are particularly important for search engine optimization.

Images10.0

100% of images have a clearly defined size

No images are being resized by the browser

  • All images have defined sizes using width and height attributes in the HTML. These attributes are optional, but strongly recommended as they help the browser arrange the page faster.

Freshness10.0

Last updated April 1, 2024

  • It looks like this website was last updated on Monday, April 1, 2024. This is good because visitors perceive up-to-date websites as more credible. Websites that are updated regularly are also spidered by search engines more often.
  • To find this information we used the last modified dates reported by this website's server in addition to looking for dates written on each page.

All dates found

DateFileSource
4/1/24phpooey.com/Body text
4/1/24www.phpooey.com/index.phpBody text
3/1/24www.phpooey.com/index.php/.../Body text

Popularityi

  • Sorry, it was not possible to determine the popularity for this website.

Source: Ahrefs

Domain agei

  • Sorry, we cannot check the domain age of .com websites.

Fast, branded website audits

Insites creates professional website reports that can be shared with your clients.

How does Insites compare?

Tests 17 fixed tests 50+ testsCovers SEO, SEM, Google My Business, reviews, social media and much more
Add your brandingNoYes
Export & shareNoPDF & link
Lead generationNoEmbed on your site
Competitor auditsNoYes
Test as a batchNoYes
Integrations + APINoYes
Multi-lingualNo20+ languages
Try it free