Tools & Wizards About Us
metromobile.com screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 57

    SEO

    Google-friendlier than
    20% of websites

metromobile.com

Motorola and Kenwood Two-Way Radio Services | Metro Mobile

Page Load Speed

2.4 sec in total

First Response

246 ms

Resources Loaded

1.9 sec

Page Rendered

220 ms

metromobile.com screenshot

About Website

Welcome to metromobile.com homepage info - get ready to check Metro Mobile best content right away, or after learning these important things about metromobile.com

Metro Mobile is an authorized dealer of Kenwood and Motorola two-way radio communication systems in the San Francisco Bay Area.

Visit metromobile.com

Key Findings

We analyzed Metromobile.com page load time and found that the first response time was 246 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

metromobile.com performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.133

81/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

metromobile.com

246 ms

metromobile.com

270 ms

www.metromobile.com

296 ms

www.metromobile.com

279 ms

bootstrap.min.css

36 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 80% of them (36 requests) were addressed to the original Metromobile.com, 11% (5 requests) were made to Cdn.jsdelivr.net and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (584 ms) belongs to the original domain Metromobile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.1 kB (23%)

Content Size

950.6 kB

After Optimization

732.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 16.4 kB

  • Original 21.2 kB
  • After minification 17.9 kB
  • After compression 4.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 3.3 kB, which is 15% 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 16.4 kB or 78% of the original size.

Image Optimization

-19%

Potential reduce by 161.8 kB

  • Original 865.5 kB
  • After minification 703.8 kB

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. Obviously, Metro Mobile needs image optimization as it can save up to 161.8 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 2.2 kB

  • Original 20.3 kB
  • After minification 19.6 kB
  • After compression 18.1 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 2.2 kB or 11% of the original size.

CSS Optimization

-86%

Potential reduce by 37.7 kB

  • Original 43.5 kB
  • After minification 31.2 kB
  • After compression 5.9 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. Metromobile.com needs all CSS files to be minified and compressed as it can save up to 37.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (18%)

Requests Now

39

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

metromobile.com

metromobile.com

246 ms

metromobile.com

metromobile.com

270 ms

www.metromobile.com

www.metromobile.com

296 ms

www.metromobile.com

www.metromobile.com

279 ms

bootstrap.min.css

bootstrap.min.css

36 ms

slick-theme.css

slick-theme.css

22 ms

slick.css

slick.css

24 ms

styles.css

styles.css

133 ms

jquery.min.js

jquery.min.js

34 ms

slick.min.js

slick.min.js

24 ms

main.js

main.js

190 ms

stylesheet.css

stylesheet.css

76 ms

ga.js

ga.js

86 ms

4.jpg

4.jpg

194 ms

header_bg.jpg

header_bg.jpg

191 ms

nav_bg.png

nav_bg.png

191 ms

nav_divider.png

nav_divider.png

185 ms

5.jpg

5.jpg

325 ms

1.jpg

1.jpg

329 ms

2.jpg

2.jpg

349 ms

3.jpg

3.jpg

358 ms

4.jpg

4.jpg

318 ms

motorola.jpg

motorola.jpg

269 ms

safety.jpg

safety.jpg

339 ms

dispatch.jpg

dispatch.jpg

402 ms

rentals.jpg

rentals.jpg

406 ms

helmet.jpg

helmet.jpg

416 ms

belmont-office.png

belmont-office.png

436 ms

customer_police.png

customer_police.png

429 ms

customer_fire.png

customer_fire.png

438 ms

customer_construction.png

customer_construction.png

475 ms

customer_facilities.png

customer_facilities.png

488 ms

customer_hospitality.png

customer_hospitality.png

496 ms

customer_fleet.png

customer_fleet.png

496 ms

customer_education.png

customer_education.png

508 ms

EMS_Command_center_IMG_5307_270.png

EMS_Command_center_IMG_5307_270.png

506 ms

customer_utilities.png

customer_utilities.png

548 ms

motorcyclethumb.jpg

motorcyclethumb.jpg

584 ms

system_radios.jpg

system_radios.jpg

579 ms

kenwood_p25.jpg

kenwood_p25.jpg

566 ms

footer_logo.png

footer_logo.png

574 ms

ajax-loader.gif

ajax-loader.gif

58 ms

slick.woff

slick.woff

17 ms

bauhausm_1-webfont.woff

bauhausm_1-webfont.woff

523 ms

__utm.gif

__utm.gif

12 ms

Accessibility Review

metromobile.com accessibility score

89

Accessibility Issues

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

metromobile.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

metromobile.com SEO score

57

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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 Metromobile.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 Metromobile.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

metromobile.com

Open Graph description is not detected on the main page of Metro Mobile. 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: