Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

citybug.com

CITYBUG

Page Load Speed

14.5 sec in total

First Response

457 ms

Resources Loaded

13.8 sec

Page Rendered

206 ms

citybug.com screenshot

About Website

Click here to check amazing CITYBUG content for United States. Otherwise, check out these important facts you probably never knew about citybug.com

Citybug2 was designed with the utmost care, with a less-is-more philosophy in mind. Its sleek and minimalistic style is expressed in the dynamic and elegant cover that neatly hides the plethora of adv...

Visit citybug.com

Key Findings

We analyzed Citybug.com page load time and found that the first response time was 457 ms and then it took 14 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

citybug.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value18.4 s

0/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.151

75/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

citybug.com

457 ms

www.citybug.com

3196 ms

new_top.css

1451 ms

jquery-ui.css

1654 ms

citybug.css

1653 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 88% of them (36 requests) were addressed to the original Citybug.com, 10% (4 requests) were made to Use.typekit.net and 2% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Citybug.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 465.5 kB (20%)

Content Size

2.3 MB

After Optimization

1.8 MB

In fact, the total size of Citybug.com main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 34.7 kB

  • Original 52.5 kB
  • After minification 41.6 kB
  • After compression 17.8 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 10.9 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 34.7 kB or 66% of the original size.

Image Optimization

-3%

Potential reduce by 57.7 kB

  • Original 1.7 MB
  • After minification 1.7 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. CITYBUG images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 225.7 kB

  • Original 360.2 kB
  • After minification 327.6 kB
  • After compression 134.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 225.7 kB or 63% of the original size.

CSS Optimization

-90%

Potential reduce by 147.4 kB

  • Original 164.1 kB
  • After minification 110.5 kB
  • After compression 16.7 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Citybug.com needs all CSS files to be minified and compressed as it can save up to 147.4 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (56%)

Requests Now

36

After Optimization

16

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CITYBUG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

citybug.com accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

Best Practices

citybug.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

citybug.com SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citybug.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Citybug.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of CITYBUG. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: