Site Desk



Enter domain


← Click to update
weblogs.com

Website review weblogs.com

 Generated on October 06 2016 06:55 AM

Old statistics? UPDATE !


The score is 44/100

Download PDF Version

SEO Content
Title

Weblogs.com : Weblogs



Length : 21

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



Length : 0

Very bad. We haven't found meta description on your page. Use this free online meta tags generator to create description.
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 This page does not take advantage of Og Properties. This tags allows social crawler's better structurize your page. Use this free og properties generator to create them.
Headings
H1 H2 H3 H4 H5 H6
0 0 1 0 0 0
  • [H3] Recently Updated Weblogs...
Images We found 6 images on this web page.

6 alt attributes are empty or missing. Add alternative text so that search engines can better understand the content of your images.
Text/HTML Ratio Ratio : 26%

Ideal! This page's ratio of text to HTML code is between 25 and 70 percent.
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 8 links including 0 link(s) to files



Anchor Type Juice
Home Internal Passing Juice
About Us Internal Passing Juice
FAQ Internal Passing Juice
API Internal Passing Juice
Resources Internal Passing Juice
Feed Validator External Passing Juice
ping Internal Passing Juice
www.lexisnexis.com/terms/general.aspx External Passing Juice

SEO Keywords
Keywords Cloud created publicly site ping weblogs lexisnexis weblog conditions works derivative
Keywords Consistency
Keyword Content Title Keywords Description Headings
lexisnexis 5
weblogs 3
created 2
publicly 2
site 2

Usability
Url Domain : weblogs.com
Length : 11
Favicon Great, your website has a favicon.
Printability We could not find a Print-Friendly CSS.
Language You have not specified the language. Use this free meta tags generator to declare the intended language of your website.
Dublin Core This page does not take advantage of Dublin Core.

Document
Doctype HTML 4.01 Transitional
Encoding Perfect. Your declared charset is UTF-8.
W3C Validity Errors : 41
Warnings : 17
Email Privacy Great no email address has been found in plain text!
Deprecated HTML Great! We haven't found deprecated HTML tags in your HTML.
Speed Tips
Attention! Try to avoid nested tables in HTML.
Too bad, your website is using inline styles.
Great, your website has few CSS files.
Too bad, your website has too many JS files (more than 6).
Too bad, your website does not take advantage of gzip.

Mobile
Mobile Optimization
Apple Icon
Meta Viewport Tag
Flash content

Optimization
XML Sitemap Missing

Your website does not have an XML sitemap - this can be problematic.

A sitemap lists URLs that are available for crawling and can include additional information like your site's latest updates, frequency of changes and importance of the URLs. This allows search engines to crawl the site more intelligently.
Robots.txt http://weblogs.com/robots.txt

Great, your website has a robots.txt file.
Analytics Great, your website has an analytics tool.

   Google Analytics

PageSpeed Insights

47 / 100    Speed
  Should Fix:
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 368.6KiB (62% reduction).

  • Compressing http://weblogs.com/fonts/OmnesSemiBold.otf could save 54.9KiB (43% reduction).
  • Compressing http://weblogs.com/fonts/Omnes-Regular.otf could save 52.2KiB (46% reduction).
  • Compressing http://rpc.weblogs.com/js/prototype.js could save 37.8KiB (78% reduction).
  • Compressing http://weblogs.com/js/prototype.js could save 37.8KiB (78% reduction).
  • Compressing http://rpc.weblogs.com/js/effects.js could save 26.2KiB (79% reduction).
  • Compressing http://weblogs.com/js/effects.js could save 26.2KiB (79% reduction).
  • Compressing http://rpc.weblogs.com/js/controls.js could save 19.5KiB (74% reduction).
  • Compressing http://weblogs.com/js/controls.js could save 19.5KiB (74% reduction).
  • Compressing http://rpc.weblogs.com/js/dragdrop.js could save 14.2KiB (75% reduction).
  • Compressing http://weblogs.com/js/dragdrop.js could save 14.2KiB (75% reduction).
  • Compressing http://rpc.weblogs.com/js/slider.js could save 7.7KiB (71% reduction).
  • Compressing http://weblogs.com/js/slider.js could save 7.7KiB (71% reduction).
  • Compressing http://weblogs.com/css/wwwprocessor.css could save 7.2KiB (75% reduction).
  • Compressing http://weblogs.com/ could save 6.1KiB (71% reduction).
  • Compressing http://rpc.weblogs.com/js/behaviour.js could save 5.5KiB (69% reduction).
  • Compressing http://weblogs.com/js/behaviour.js could save 5.5KiB (69% reduction).
  • Compressing http://rpc.weblogs.com/js/jslog.js could save 4KiB (62% reduction).
  • Compressing http://weblogs.com/js/jslog.js could save 4KiB (62% reduction).
  • Compressing http://weblogs.com/js/BloggingTabBehavior.js could save 2.5KiB (65% reduction).
  • Compressing http://rpc.weblogs.com/js/xmlhttp.js could save 2.4KiB (74% reduction).
  • Compressing http://weblogs.com/js/xmlhttp.js could save 2.4KiB (74% reduction).
  • Compressing http://rpc.weblogs.com/js/pingSiteForm.js could save 2.3KiB (69% reduction).
  • Compressing http://rpc.weblogs.com/js/builder.js could save 2.2KiB (65% reduction).
  • Compressing http://weblogs.com/js/builder.js could save 2.2KiB (65% reduction).
  • Compressing http://weblogs.com/js/weblogs.js could save 1.5KiB (57% reduction).
  • Compressing http://rpc.weblogs.com/js/scriptaculous.js could save 1,002B (46% reduction).
  • Compressing http://weblogs.com/js/scriptaculous.js could save 1,002B (46% reduction).
  • Compressing http://weblogs.com/js/viewport.js could save 864B (57% 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:

  • http://rpc.weblogs.com/images/file_folder.jpg (expiration not specified)
  • http://rpc.weblogs.com/js/behaviour.js (expiration not specified)
  • http://rpc.weblogs.com/js/builder.js (expiration not specified)
  • http://rpc.weblogs.com/js/controls.js (expiration not specified)
  • http://rpc.weblogs.com/js/dragdrop.js (expiration not specified)
  • http://rpc.weblogs.com/js/effects.js (expiration not specified)
  • http://rpc.weblogs.com/js/jslog.js (expiration not specified)
  • http://rpc.weblogs.com/js/pingSiteForm.js (expiration not specified)
  • http://rpc.weblogs.com/js/prototype.js (expiration not specified)
  • http://rpc.weblogs.com/js/scriptaculous.js (expiration not specified)
  • http://rpc.weblogs.com/js/slider.js (expiration not specified)
  • http://rpc.weblogs.com/js/xmlhttp.js (expiration not specified)
  • http://weblogs.com/css/wwwprocessor.css (expiration not specified)
  • http://weblogs.com/images/Weblogs_Pingserver.gif (expiration not specified)
  • http://weblogs.com/images/changes_xml.png (expiration not specified)
  • http://weblogs.com/images/file_folder.jpg (expiration not specified)
  • http://weblogs.com/images/scrolling_list.png (expiration not specified)
  • http://weblogs.com/images/send_a_ping.png (expiration not specified)
  • http://weblogs.com/js/BloggingTabBehavior.js (expiration not specified)
  • http://weblogs.com/js/behaviour.js (expiration not specified)
  • http://weblogs.com/js/builder.js (expiration not specified)
  • http://weblogs.com/js/controls.js (expiration not specified)
  • http://weblogs.com/js/dragdrop.js (expiration not specified)
  • http://weblogs.com/js/effects.js (expiration not specified)
  • http://weblogs.com/js/jslog.js (expiration not specified)
  • http://weblogs.com/js/prototype.js (expiration not specified)
  • http://weblogs.com/js/scriptaculous.js (expiration not specified)
  • http://weblogs.com/js/slider.js (expiration not specified)
  • http://weblogs.com/js/viewport.js (expiration not specified)
  • http://weblogs.com/js/weblogs.js (expiration not specified)
  • http://weblogs.com/js/xmlhttp.js (expiration not specified)
  • http://www.google-analytics.com/ga.js (2 hours)
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 107.6KiB (33% reduction).

  • Minifying http://rpc.weblogs.com/js/prototype.js could save 14.1KiB (30% reduction).
  • Minifying http://weblogs.com/js/prototype.js could save 14.1KiB (30% reduction).
  • Minifying http://rpc.weblogs.com/js/controls.js could save 9.6KiB (37% reduction).
  • Minifying http://weblogs.com/js/controls.js could save 9.6KiB (37% reduction).
  • Minifying http://rpc.weblogs.com/js/effects.js could save 8.5KiB (26% reduction).
  • Minifying http://weblogs.com/js/effects.js could save 8.5KiB (26% reduction).
  • Minifying http://rpc.weblogs.com/js/dragdrop.js could save 5.7KiB (31% reduction).
  • Minifying http://weblogs.com/js/dragdrop.js could save 5.7KiB (31% reduction).
  • Minifying http://rpc.weblogs.com/js/behaviour.js could save 4.5KiB (56% reduction).
  • Minifying http://weblogs.com/js/behaviour.js could save 4.5KiB (56% reduction).
  • Minifying http://rpc.weblogs.com/js/slider.js could save 3.7KiB (35% reduction).
  • Minifying http://weblogs.com/js/slider.js could save 3.7KiB (35% reduction).
  • Minifying http://rpc.weblogs.com/js/xmlhttp.js could save 2.1KiB (67% reduction).
  • Minifying http://weblogs.com/js/xmlhttp.js could save 2.1KiB (67% reduction).
  • Minifying http://rpc.weblogs.com/js/builder.js could save 1.5KiB (43% reduction).
  • Minifying http://weblogs.com/js/builder.js could save 1.5KiB (43% reduction).
  • Minifying http://rpc.weblogs.com/js/scriptaculous.js could save 1.4KiB (64% reduction).
  • Minifying http://weblogs.com/js/scriptaculous.js could save 1.4KiB (64% reduction).
  • Minifying http://weblogs.com/js/BloggingTabBehavior.js could save 1.2KiB (32% reduction).
  • Minifying http://rpc.weblogs.com/js/pingSiteForm.js could save 984B (30% reduction).
  • Minifying http://weblogs.com/js/weblogs.js could save 980B (37% reduction).
  • Minifying http://rpc.weblogs.com/js/jslog.js could save 929B (15% reduction).
  • Minifying http://weblogs.com/js/jslog.js could save 929B (15% reduction).
  • Minifying http://weblogs.com/js/viewport.js could save 583B (39% reduction).
Show how to fix
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 14 blocking script resources and 1 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:

  • http://weblogs.com/js/prototype.js
  • http://weblogs.com/js/scriptaculous.js
  • http://weblogs.com/js/builder.js
  • http://weblogs.com/js/effects.js
  • http://weblogs.com/js/dragdrop.js
  • http://weblogs.com/js/controls.js
  • http://weblogs.com/js/slider.js
  • http://weblogs.com/js/effects.js
  • http://weblogs.com/js/behaviour.js
  • http://weblogs.com/js/jslog.js
  • http://weblogs.com/js/xmlhttp.js
  • http://weblogs.com/js/viewport.js
  • http://weblogs.com/js/weblogs.js
  • http://weblogs.com/js/BloggingTabBehavior.js

Optimize CSS Delivery of the following:

  • http://weblogs.com/css/wwwprocessor.css
Show how to fix
  Consider Fixing:
Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 2.3KiB (25% reduction).

  • Minifying http://weblogs.com/css/wwwprocessor.css could save 2.3KiB (25% reduction).
Show how to fix
Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 3.2KiB (38% reduction).

  • Minifying http://weblogs.com/ could save 3.2KiB (38% reduction).
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 3.1KiB (26% reduction).

  • Compressing http://weblogs.com/images/Weblogs_Pingserver.gif could save 1.4KiB (22% reduction).
  • Compressing http://weblogs.com/images/scrolling_list.png could save 977B (40% reduction).
  • Compressing http://weblogs.com/images/changes_xml.png could save 757B (23% reduction).
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.

Reduce server response time

Your server responded quickly. Learn more about server response time optimization.

Prioritize visible content

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

64 / 100    User Experience
  Should Fix:
Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Show how to fix
Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

  • Feed Validator and 5 others render only 5 pixels tall (12 CSS pixels) final.
  • See what's changing and 2 others render only 5 pixels tall (12 CSS pixels) final.
  • Weblog change lists and 2 others render only 5 pixels tall (12 CSS pixels) final.
  • Recently Updated Weblogs... renders only 5 pixels tall (14 CSS pixels) final.
  • ed or distribu…ghts reserved. and 3 others render only 4 pixels tall (11 CSS pixels) final.
  • www.lexisnexis…s/general.aspx renders only 4 pixels tall (11 CSS pixels) final.
Show how to fix
  Consider Fixing:
Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

  • The tap target <a href="home.html" class="nav">Home</a> and 5 others are close to other tap targets final.
Show how to fix
  3 Passed Rules
Show details
Avoid app install interstitials that hide content

Your page does not appear to have any app install interstitials that hide a significant amount of content. Learn more about the importance of avoiding the use of app install interstitials.

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.

58 / 100    Speed
  Should Fix:
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 368.6KiB (62% reduction).

  • Compressing http://weblogs.com/fonts/OmnesSemiBold.otf could save 54.9KiB (43% reduction).
  • Compressing http://weblogs.com/fonts/Omnes-Regular.otf could save 52.2KiB (46% reduction).
  • Compressing http://rpc.weblogs.com/js/prototype.js could save 37.8KiB (78% reduction).
  • Compressing http://weblogs.com/js/prototype.js could save 37.8KiB (78% reduction).
  • Compressing http://rpc.weblogs.com/js/effects.js could save 26.2KiB (79% reduction).
  • Compressing http://weblogs.com/js/effects.js could save 26.2KiB (79% reduction).
  • Compressing http://rpc.weblogs.com/js/controls.js could save 19.5KiB (74% reduction).
  • Compressing http://weblogs.com/js/controls.js could save 19.5KiB (74% reduction).
  • Compressing http://rpc.weblogs.com/js/dragdrop.js could save 14.2KiB (75% reduction).
  • Compressing http://weblogs.com/js/dragdrop.js could save 14.2KiB (75% reduction).
  • Compressing http://rpc.weblogs.com/js/slider.js could save 7.7KiB (71% reduction).
  • Compressing http://weblogs.com/js/slider.js could save 7.7KiB (71% reduction).
  • Compressing http://weblogs.com/css/wwwprocessor.css could save 7.2KiB (75% reduction).
  • Compressing http://weblogs.com/ could save 6.1KiB (71% reduction).
  • Compressing http://rpc.weblogs.com/js/behaviour.js could save 5.5KiB (69% reduction).
  • Compressing http://weblogs.com/js/behaviour.js could save 5.5KiB (69% reduction).
  • Compressing http://rpc.weblogs.com/js/jslog.js could save 4KiB (62% reduction).
  • Compressing http://weblogs.com/js/jslog.js could save 4KiB (62% reduction).
  • Compressing http://weblogs.com/js/BloggingTabBehavior.js could save 2.5KiB (65% reduction).
  • Compressing http://rpc.weblogs.com/js/xmlhttp.js could save 2.4KiB (74% reduction).
  • Compressing http://weblogs.com/js/xmlhttp.js could save 2.4KiB (74% reduction).
  • Compressing http://rpc.weblogs.com/js/pingSiteForm.js could save 2.3KiB (69% reduction).
  • Compressing http://rpc.weblogs.com/js/builder.js could save 2.2KiB (65% reduction).
  • Compressing http://weblogs.com/js/builder.js could save 2.2KiB (65% reduction).
  • Compressing http://weblogs.com/js/weblogs.js could save 1.5KiB (57% reduction).
  • Compressing http://rpc.weblogs.com/js/scriptaculous.js could save 1,002B (46% reduction).
  • Compressing http://weblogs.com/js/scriptaculous.js could save 1,002B (46% reduction).
  • Compressing http://weblogs.com/js/viewport.js could save 864B (57% 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:

  • http://rpc.weblogs.com/images/file_folder.jpg (expiration not specified)
  • http://rpc.weblogs.com/js/behaviour.js (expiration not specified)
  • http://rpc.weblogs.com/js/builder.js (expiration not specified)
  • http://rpc.weblogs.com/js/controls.js (expiration not specified)
  • http://rpc.weblogs.com/js/dragdrop.js (expiration not specified)
  • http://rpc.weblogs.com/js/effects.js (expiration not specified)
  • http://rpc.weblogs.com/js/jslog.js (expiration not specified)
  • http://rpc.weblogs.com/js/pingSiteForm.js (expiration not specified)
  • http://rpc.weblogs.com/js/prototype.js (expiration not specified)
  • http://rpc.weblogs.com/js/scriptaculous.js (expiration not specified)
  • http://rpc.weblogs.com/js/slider.js (expiration not specified)
  • http://rpc.weblogs.com/js/xmlhttp.js (expiration not specified)
  • http://weblogs.com/css/wwwprocessor.css (expiration not specified)
  • http://weblogs.com/images/Weblogs_Pingserver.gif (expiration not specified)
  • http://weblogs.com/images/changes_xml.png (expiration not specified)
  • http://weblogs.com/images/file_folder.jpg (expiration not specified)
  • http://weblogs.com/images/scrolling_list.png (expiration not specified)
  • http://weblogs.com/images/send_a_ping.png (expiration not specified)
  • http://weblogs.com/js/BloggingTabBehavior.js (expiration not specified)
  • http://weblogs.com/js/behaviour.js (expiration not specified)
  • http://weblogs.com/js/builder.js (expiration not specified)
  • http://weblogs.com/js/controls.js (expiration not specified)
  • http://weblogs.com/js/dragdrop.js (expiration not specified)
  • http://weblogs.com/js/effects.js (expiration not specified)
  • http://weblogs.com/js/jslog.js (expiration not specified)
  • http://weblogs.com/js/prototype.js (expiration not specified)
  • http://weblogs.com/js/scriptaculous.js (expiration not specified)
  • http://weblogs.com/js/slider.js (expiration not specified)
  • http://weblogs.com/js/viewport.js (expiration not specified)
  • http://weblogs.com/js/weblogs.js (expiration not specified)
  • http://weblogs.com/js/xmlhttp.js (expiration not specified)
  • http://www.google-analytics.com/ga.js (2 hours)
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 107.6KiB (33% reduction).

  • Minifying http://rpc.weblogs.com/js/prototype.js could save 14.1KiB (30% reduction).
  • Minifying http://weblogs.com/js/prototype.js could save 14.1KiB (30% reduction).
  • Minifying http://rpc.weblogs.com/js/controls.js could save 9.6KiB (37% reduction).
  • Minifying http://weblogs.com/js/controls.js could save 9.6KiB (37% reduction).
  • Minifying http://rpc.weblogs.com/js/effects.js could save 8.5KiB (26% reduction).
  • Minifying http://weblogs.com/js/effects.js could save 8.5KiB (26% reduction).
  • Minifying http://rpc.weblogs.com/js/dragdrop.js could save 5.7KiB (31% reduction).
  • Minifying http://weblogs.com/js/dragdrop.js could save 5.7KiB (31% reduction).
  • Minifying http://rpc.weblogs.com/js/behaviour.js could save 4.5KiB (56% reduction).
  • Minifying http://weblogs.com/js/behaviour.js could save 4.5KiB (56% reduction).
  • Minifying http://rpc.weblogs.com/js/slider.js could save 3.7KiB (35% reduction).
  • Minifying http://weblogs.com/js/slider.js could save 3.7KiB (35% reduction).
  • Minifying http://rpc.weblogs.com/js/xmlhttp.js could save 2.1KiB (67% reduction).
  • Minifying http://weblogs.com/js/xmlhttp.js could save 2.1KiB (67% reduction).
  • Minifying http://rpc.weblogs.com/js/builder.js could save 1.5KiB (43% reduction).
  • Minifying http://weblogs.com/js/builder.js could save 1.5KiB (43% reduction).
  • Minifying http://rpc.weblogs.com/js/scriptaculous.js could save 1.4KiB (64% reduction).
  • Minifying http://weblogs.com/js/scriptaculous.js could save 1.4KiB (64% reduction).
  • Minifying http://weblogs.com/js/BloggingTabBehavior.js could save 1.2KiB (32% reduction).
  • Minifying http://rpc.weblogs.com/js/pingSiteForm.js could save 984B (30% reduction).
  • Minifying http://weblogs.com/js/weblogs.js could save 980B (37% reduction).
  • Minifying http://rpc.weblogs.com/js/jslog.js could save 929B (15% reduction).
  • Minifying http://weblogs.com/js/jslog.js could save 929B (15% reduction).
  • Minifying http://weblogs.com/js/viewport.js could save 583B (39% reduction).
Show how to fix
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 14 blocking script resources and 1 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:

  • http://weblogs.com/js/prototype.js
  • http://weblogs.com/js/scriptaculous.js
  • http://weblogs.com/js/builder.js
  • http://weblogs.com/js/effects.js
  • http://weblogs.com/js/dragdrop.js
  • http://weblogs.com/js/controls.js
  • http://weblogs.com/js/slider.js
  • http://weblogs.com/js/effects.js
  • http://weblogs.com/js/behaviour.js
  • http://weblogs.com/js/jslog.js
  • http://weblogs.com/js/xmlhttp.js
  • http://weblogs.com/js/viewport.js
  • http://weblogs.com/js/weblogs.js
  • http://weblogs.com/js/BloggingTabBehavior.js

Optimize CSS Delivery of the following:

  • http://weblogs.com/css/wwwprocessor.css
Show how to fix
  Consider Fixing:
Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 2.3KiB (25% reduction).

  • Minifying http://weblogs.com/css/wwwprocessor.css could save 2.3KiB (25% reduction).
Show how to fix
Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 3.2KiB (38% reduction).

  • Minifying http://weblogs.com/ could save 3.2KiB (38% reduction).
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 3.1KiB (26% reduction).

  • Compressing http://weblogs.com/images/Weblogs_Pingserver.gif could save 1.4KiB (22% reduction).
  • Compressing http://weblogs.com/images/scrolling_list.png could save 977B (40% reduction).
  • Compressing http://weblogs.com/images/changes_xml.png could save 757B (23% reduction).
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.

Reduce server response time

Your server responded quickly. Learn more about server response time optimization.

Prioritize visible content

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

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

Site Desk