Actor Website Review


Enter domain


← Click to update

jamesmiller.us

Website review jamesmiller.us

 Generated on August 14 2019 01:46 AM

Old statistics? UPDATE !


The score is 64/100

Download PDF Version

SEO Content

Title

Los Angeles | James Thomas Miller Actor



Length : 39

Perfect, your title contains between 10 and 70 characters.
Description

Official site of Los Angeles based actor James Thomas Miller. Miller is a BFA trained actor and singer specializing in comedy on both stage and screen, musical theatre, and a cappella music.



Length : 190

Ideally, your meta description should contain between 70 and 160 characters (spaces included). Use this free tool to calculate text length.
Keywords



Very bad. We haven't found meta keywords on your page. Use this free online meta tags generator to create keywords.
Og Meta Properties Good, your page take advantage of Og Properties.
Property Content
title Los Angeles | James Thomas Miller Actor
description Official site of Los Angeles based actor James Thomas Miller. Miller is a BFA trained actor and singer specializing in comedy on both stage and screen, musical theatre, and a cappella music.
image https://static.wixstatic.com/media/584ae0_2c1d36650bf14da6bc2274ddd76f54f0~mv2_d_6000_3376_s_4_2.jpg/v1/fill/w_6000,h_3376,al_c/584ae0_2c1d36650bf14da6bc2274ddd76f54f0~mv2_d_6000_3376_s_4_2.jpg
image:width 6000
image:height 3376
url https://www.jamesmiller.us
site_name Actor Site
type website
Headings
H1 H2 H3 H4 H5 H6
0 1 0 0 0 2
  • [H2] JAMES THOMAS MILLER
  • [H6] ACTOR . SINGER . WRITER
  • [H6]  Los Angeles, CA
Images We found 4 images on this web page.

Good, most or all of your images have alt attributes
Text/HTML Ratio Ratio : 0%

This page's ratio of text to HTML code is below 15 percent, this means that your website probably needs more text content.
Flash Perfect, no Flash content has been detected on this page.
Iframe Too Bad, you have Iframes on the web pages, this mean that content in an Iframe cannot be indexed.

URL Rewrite Good. Your links looks friendly!
Underscores in the URLs Perfect! No underscores detected in your URLs.
In-page links We found a total of 0 links including 0 link(s) to files



Anchor Type Juice

SEO Keywords

Keywords Cloud writer reel  los singer james angeles thomas miller  2019 actor
Keywords Consistency
Keyword Content Title Keywords Description Headings
thomas 3
james 3
miller 3
angeles 2
actor 2

Usability

Url Domain : jamesmiller.us
Length : 14
Favicon Great, your website has a favicon.
Printability We could not find a Print-Friendly CSS.
Language Good. Your declared language is en.
Dublin Core This page does not take advantage of Dublin Core.

Document

Doctype HTML 5
Encoding Perfect. Your declared charset is UTF-8.
W3C Validity Errors : 130
Warnings : 26
Email Privacy Warning! At least one email address has been found in the plain text. Use free antispam protector to hide email from spammers.
Deprecated HTML Great! We haven't found deprecated HTML tags in your HTML.
Speed Tips
Excellent, your website doesn't use nested tables.
Too bad, your website is using inline styles.
Great, your website has few CSS files.
Perfect, your website has few JavaScript files.
Too bad, your website does not take advantage of gzip.

Mobile

Mobile Optimization
Apple Icon
Meta Viewport Tag
Flash content

Optimization

XML Sitemap Great, your website has an XML sitemap.

https://www.jamesmiller.us/sitemap.xml
Robots.txt http://jamesmiller.us/robots.txt

Great, your website has a robots.txt file.
Analytics Missing

We didn't detect an analytics tool installed on this website.

Web analytics let you measure visitor activity on your website. You should have at least one analytics tool installed, but It can also be good to install a second in order to cross-check the data.

PageSpeed Insights


91 / 100    Speed
  Consider Fixing:
Reduce server response time
In our test, your server responded in 0.48 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Show how to fix
Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 647B (40% reduction).

  • Minifying https://static.parastorage.com/unpkg/wix-ui-santa@1.0.1011/dist/statics/dataRefs.bundle.js could save 647B (40% reduction) after compression.
Show how to fix
Optimize images
Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 42.9KiB (64% reduction).

  • Compressing https://static.wixstatic.com/media/584ae0_2c1d36650bf14da6bc2274ddd76f54f0~mv2_d_6000_3376_s_4_2.jpg/v1/crop/x_0,y_269,w_6000,h_2838/fill/w_326,h_235,al_c,q_80,usm_0.66_1.00_0.01/HeroPhoto19.jpg could save 42KiB (65% reduction).
  • Compressing https://static.parastorage.com/services/skins/2.1229.80/images/wysiwyg/core/themes/viewer/spotify/spotify_follow_placeholder_basic_all_hide.png could save 961B (41% reduction).
Show how to fix
  7 Passed Rules
Show details
Avoid landing page redirects

Your page has no redirects. Learn more about avoiding landing page redirects.

Enable compression

You have compression enabled. Learn more about enabling compression.

Leverage browser caching

You have enabled browser caching. Learn more about browser caching recommendations.

Minify CSS

Your CSS is minified. Learn more about minifying CSS.

Minify HTML

Your HTML is minified. Learn more about minifying HTML.

Eliminate render-blocking JavaScript and CSS in above-the-fold content

You have no render-blocking resources. Learn more about removing render-blocking resources.

Prioritize visible content

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.


96 / 100    User Experience
  Consider Fixing:
Configure the viewport
Your page specifies a fixed-width mobile viewport. Consider using a responsive viewport to allow your page to render properly on all devices.

Configuring a viewport specifying width=device-width instead of width=320 will allow your page to adapt for devices of various widths. This may require additional work if the styling on your page relies on a fixed-width layout.

Show how to fix
  4 Passed Rules
Show details
Avoid plugins

Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.

Size content to viewport

The contents of your page fit within the viewport. Learn more about sizing content to the viewport.

Size tap targets appropriately

All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.

Use legible font sizes

The text on your page is legible. Learn more about using legible font sizes.


77 / 100    Speed
  Should Fix:
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

  • https://static.parastorage.com/unpkg/core-js@2.6.9/client/shim.min.js
  • https://static.parastorage.com/polyfill/v3/polyfill.min.js?features=fetch&flags=always,gated&unknown=polyfill&rum=0

Optimize CSS Delivery of the following:

  • https://static.parastorage.com/services/wix-bolt/1.3418.0/node_modules/wix-santa/static/css/viewer.min.css
  • https://static.parastorage.com/services/santa-resources/resources/viewer/user-site-fonts/v7/languages.css
  • https://fonts.googleapis.com/css?family=Anton:n,b,i,bi|Basic:n,b,i,bi|Caudex:n,b,i,bi|Chelsea+Market:n,b,i,bi|Corben:n,b,i,bi|EB+Garamond:n,b,i,bi|Enriqueta:n,b,i,bi|Forum:n,b,i,bi|Fredericka+the+Great:n,b,i,bi|Jockey+One:n,b,i,bi|Josefin+Slab:n,b,i,bi|Jura:n,b,i,bi|Kelly+Slab:n,b,i,bi|Marck+Script:n,b,i,bi|Lobster:n,b,i,bi|Mr+De+Haviland:n,b,i,bi|Niconne:n,b,i,bi|Noticia+Text:n,b,i,bi|Overlock:n,b,i,bi|Patrick+Hand:n,b,i,bi|Play:n,b,i,bi|Sarina:n,b,i,bi|Signika:n,b,i,bi|Spinnaker:n,b,i,bi|Monoton:n,b,i,bi|Sacramento:n,b,i,bi|Cookie:n,b,i,bi|Raleway:n,b,i,bi|Open+Sans+Condensed:300:n,b,i,bi|Amatic+SC:n,b,i,bi|Cinzel:n,b,i,bi|Sail:n,b,i,bi|Playfair+Display:n,b,i,bi|Libre+Baskerville:n,b,i,bi|Roboto:n,b,i,bi|Roboto:n,b,i,bi|Roboto:n,b,i,bi|Work+Sans:n,b,i,bi|Work+Sans:n,b,i,bi|Poppins:n,b,i,bi|Poppins:n,b,i,bi|Barlow:n,b,i,bi|Barlow:n,b,i,bi|Oswald:n,b,i,bi|Oswald:n,b,i,bi|Oswald:n,b,i,bi|Cormorant+Garamond:n,b,i,bi|Cormorant+Garamond:n,b,i,bi|Cormorant+Garamond:n,b,i,bi|Playfair+Display:n,b,i,bi|Dancing+Script:n,b,i,bi|Damion:n,b,i,bi|Suez+One:n,b,i,bi|Rozha+One:n,b,i,bi|Raleway:n,b,i,bi|Lato:n,b,i,bi|Questrial:n,b,i,bi|Montserrat:n,b,i,bi|&subset=latin
Show how to fix
Optimize images
Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 114.7KiB (33% reduction).

  • Compressing https://static.wixstatic.com/media/584ae0_2c1d36650bf14da6bc2274ddd76f54f0~mv2_d_6000_3376_s_4_2.jpg/v1/crop/x_0,y_269,w_6000,h_2838/fill/w_1440,h_681,al_c,q_85,usm_0.66_1.00_0.01/HeroPhoto19.jpg could save 102.7KiB (33% reduction).
  • Compressing https://i.scdn.co/image/7493ee10f28f995f372e73492ec6fbc132560ec4 could save 10.3KiB (33% reduction).
  • Compressing https://static.parastorage.com/services/skins/2.1229.80/images/wysiwyg/core/themes/viewer/spotify/spotify_follow_placeholder_basic_all_hide.png could save 961B (41% reduction).
  • Compressing https://embed.spotify.com/static/assets/images/follow/sprite@1.png could save 852B (53% reduction).
Show how to fix
  Consider Fixing:
Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 622B (45% reduction).

  • Compressing https://static.wixstatic.com/shapes/3d84bae5ad4d4d8a96de15e9f4b79a08.svg could save 622B (45% reduction).
Show how to fix
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

  • https://www.jamesmiller.us/_api/pro-gallery-webapp/v1/viewer/experiments (expiration not specified)
  • https://www.jamesmiller.us/_api/wix-code-telemetry-registry-public/v1/sites/d26efd17-f4fe-46b1-95c3-f305c065c0f6/telemetry/runtime-configuration (expiration not specified)
Show how to fix
Reduce server response time
In our test, your server responded in 0.45 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Show how to fix
Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3KiB (30% reduction).

  • Minifying https://static.parastorage.com/unpkg/wix-ui-santa@1.0.1011/dist/statics/viewerComponentService.bundle.js could save 2KiB (33% reduction) after compression.
  • Minifying https://static.parastorage.com/unpkg/wix-ui-santa@1.0.1011/dist/statics/dataRefs.bundle.js could save 647B (40% reduction) after compression.
  • Minifying https://static.parastorage.com/unpkg/gsap@2.0.2/src/minified/plugins/ScrollToPlugin.min.js could save 232B (15% reduction) after compression.
  • Minifying https://ding.wix.com/asdk/dispatcher.js could save 131B (15% reduction) after compression.
Show how to fix
Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

  • None of the final above-the-fold content could be rendered even with the full HTML response.
Show how to fix
  3 Passed Rules
Show details
Avoid landing page redirects

Your page has no redirects. Learn more about avoiding landing page redirects.

Minify CSS

Your CSS is minified. Learn more about minifying CSS.

Minify HTML

Your HTML is minified. Learn more about minifying HTML.



* The results are cached for 30s. If you have made changes to your page, please wait for 30s before re-running the test.