Inline CSS Detector: Find Inline Styles on Any Webpage

Inline CSS detector that scans any webpage for every style attribute and embedded <style> tag. Give it one URL or a list of pages and it returns element counts, CSS byte sizes, and tag-level detail: exactly which elements carry inline styles, what class and ID they have, and what the style values say.

What data does this actor extract?

Each result contains the URL, HTTP status code, page title, inline style count, style tag count, byte sizes for each type of inline CSS, a list of elements with style attributes (tag name, class, ID, and style value), and the raw content of each style tag.

Use cases

• Pre-migration audits: check how much inline CSS a site carries before switching frameworks or CMS
• SEO checks: inline styles bloat HTML and can delay first-paint rendering; find them before they affect Core Web Vitals
• Code reviews: flag pages that violate a no-inline-styles policy without reading every file
• Site-wide checks: run against a full URL list to find the worst inline CSS offenders across a domain
• QA testing: confirm inline styles were removed after a cleanup sprint

Input

Parameter	Type	Default	Description
url	string		Single URL to scan.
urls	array		List of URLs to scan, one per line. Combined with url if both are provided.
maxUrls	integer	100	Maximum number of URLs to process per run.
timeoutSecs	integer	300	Overall actor timeout in seconds.
requestTimeoutSecs	integer	30	Per-request timeout in seconds.
proxyConfiguration	object	Datacenter (Anywhere)	Proxy type and location for requests. Supports Datacenter, Residential, Special, and custom proxies. Optional.

Example input

{
    "urls": ["https://apify.com", "https://apify.com/store"],
    "maxUrls": 50,
    "requestTimeoutSecs": 30,
    "proxyConfiguration": { "useApifyProxy": true }
}

What does the output look like?

The actor stores results in a dataset. Each entry is one scanned URL:

{
    "url": "https://apify.com",
    "statusCode": 200,
    "pageTitle": "Apify: Full-Stack Web Scraping and Data Extraction Platform",
    "hasInlineCss": true,
    "inlineStyleCount": 12,
    "styleTagCount": 2,
    "inlineStyleBytes": 438,
    "styleTagBytes": 1204,
    "totalCssBytes": 1642,
    "inlineStyleElements": [
        {
            "tag": "div",
            "id": "hero",
            "cssClass": "hero-section",
            "styleValue": "background-color: #ff5733; padding: 20px;"
        }
    ],
    "styleTagContents": [".nav { display: flex; }"],
    "scrapedAt": "2025-03-05T10:30:00.000Z"
}

Field	Type	Description
url	string	Final URL after any redirects
statusCode	integer	HTTP status code
pageTitle	string	Content of the <title> tag
hasInlineCss	boolean	True if any inline CSS was found
inlineStyleCount	integer	Number of elements with style attributes
styleTagCount	integer	Number of <style> tags on the page
inlineStyleBytes	integer	Total bytes of all inline style values
styleTagBytes	integer	Total bytes of all style tag contents
totalCssBytes	integer	Combined inline CSS byte count
inlineStyleElements	array	Tag-level detail for each element with a style attribute
styleTagContents	array	Raw text of each style tag
scrapedAt	string	ISO 8601 timestamp
error	string	Error message if the page failed to load

How it works

1. The actor reads the input URL list and deduplicates entries.
2. For each URL, it sends an HTTP request with a realistic browser User-Agent.
3. The HTML is parsed using BeautifulSoup to find all style attributes and <style> tags.
4. Counts, byte sizes, and element details are computed and pushed to the dataset.
5. Errors are caught per URL so one failed page does not stop the rest.

Integrations

Connect Inline CSS Detector with other apps and services using Apify integrations. You can integrate with Make, Zapier, Slack, Airbyte, GitHub, Google Sheets, Google Drive, and many more. You can also use webhooks to trigger actions whenever results are available.

FAQ

Can this actor scan JavaScript-rendered pages? No. The actor fetches raw HTML. Styles injected by JavaScript will not appear in results. For JS-heavy sites, use a browser-based scraper.

How many URLs can I process in one run? Up to 1000 per run via maxUrls. For larger lists, split across multiple runs.

Will it pick up inline styles from WordPress plugins or page builders? Yes, as long as those styles appear in the server-rendered HTML. Client-side injections via JavaScript are not captured.

Why does inline CSS byte count matter for SEO? Inline CSS adds to HTML document size and can block or delay rendering. Trimming it helps page speed scores, which Google uses as a ranking factor.

Run this actor before a site audit, after a code review, or any time you need hard numbers on how much inline CSS a site is carrying.