Tools & Wizards About Us
textmarks.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

textmarks.com

Text Messaging for Transit Agencies - SMS Notifications | TextMarks

Page Load Speed

3.3 sec in total

First Response

70 ms

Resources Loaded

2.7 sec

Page Rendered

525 ms

textmarks.com screenshot

About Website

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

TextMarks is an SMS text messaging service used by transit agencies to deliver real time arrival information to riders by text message.

Visit textmarks.com

Key Findings

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

Performance Metrics

textmarks.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

textmarks.com

70 ms

www.textmarks.com

328 ms

branded_bootstrap.css

88 ms

tm-framework-2014.sass.css

59 ms

tm-common-2014.sass.css

61 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 16% of them (14 requests) were addressed to the original Textmarks.com, 12% (10 requests) were made to Na-ab03.marketo.com and 8% (7 requests) were made to Static.olark.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Pixel.rubiconproject.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (60%)

Content Size

2.1 MB

After Optimization

843.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Textmarks.com main page is 2.1 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. 65% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 43.4 kB

  • Original 56.3 kB
  • After minification 48.6 kB
  • After compression 12.9 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 7.7 kB, which is 14% 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 43.4 kB or 77% of the original size.

Image Optimization

-17%

Potential reduce by 88.6 kB

  • Original 531.4 kB
  • After minification 442.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, Text Marks needs image optimization as it can save up to 88.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 715.4 kB

  • Original 1.0 MB
  • After minification 784.2 kB
  • After compression 307.2 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 715.4 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 404.6 kB

  • Original 485.6 kB
  • After minification 456.3 kB
  • After compression 80.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. Textmarks.com needs all CSS files to be minified and compressed as it can save up to 404.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (61%)

Requests Now

75

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

textmarks.com

textmarks.com

70 ms

www.textmarks.com

www.textmarks.com

328 ms

branded_bootstrap.css

branded_bootstrap.css

88 ms

tm-framework-2014.sass.css

tm-framework-2014.sass.css

59 ms

tm-common-2014.sass.css

tm-common-2014.sass.css

61 ms

font-awesome.min.css

font-awesome.min.css

10 ms

css

css

26 ms

jquery.min.js

jquery.min.js

67 ms

bootstrap.js

bootstrap.js

117 ms

552670289.js

552670289.js

328 ms

tm-front.sass.css

tm-front.sass.css

56 ms

tm-home.sass.css

tm-home.sass.css

60 ms

font-awesome.min.css

font-awesome.min.css

9 ms

jquery.marquee.min.js

jquery.marquee.min.js

21 ms

forms2.js

forms2.js

121 ms

getSeal

getSeal

510 ms

ga.js

ga.js

33 ms

__utm.gif

__utm.gif

12 ms

event

event

149 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

188 ms

509 ms

TextMarks-Logo-2014-OnTrans-460x120.png

TextMarks-Logo-2014-OnTrans-460x120.png

183 ms

YDplkKf3RPA

YDplkKf3RPA

259 ms

carousel_UND.jpg

carousel_UND.jpg

203 ms

textmarks-354329.png

textmarks-354329.png

140 ms

bg-abstract-green.jpeg

bg-abstract-green.jpeg

286 ms

cantignore.png

cantignore.png

255 ms

complicatedstuff.png

complicatedstuff.png

299 ms

behindyou.png

behindyou.png

250 ms

satisfaction_seal.png

satisfaction_seal.png

202 ms

logo-care.png

logo-care.png

215 ms

logo-cta.png

logo-cta.png

217 ms

logo-dolly.png

logo-dolly.png

217 ms

logo-medtronic.png

logo-medtronic.png

217 ms

logo-microsoft.png

logo-microsoft.png

248 ms

logo-jsu.png

logo-jsu.png

221 ms

logo-ridesmart.png

logo-ridesmart.png

248 ms

logo-fedex.png

logo-fedex.png

247 ms

logo-supercuts.png

logo-supercuts.png

246 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

99 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

156 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

181 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

30 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

76 ms

getForm

getForm

205 ms

textmarks-354329.js

textmarks-354329.js

44 ms

29 ms

27 ms

siteseal_gd_3_h_l_m.gif

siteseal_gd_3_h_l_m.gif

72 ms

loader0.js

loader0.js

65 ms

munchkin-beta.js

munchkin-beta.js

21 ms

54668703a21cf7e927000046.js

54668703a21cf7e927000046.js

49 ms

4708.js

4708.js

6 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

70 ms

www-embed-player.js

www-embed-player.js

96 ms

munchkin.js

munchkin.js

13 ms

visitWebPage

visitWebPage

17 ms

tagjs

tagjs

38 ms

4347-324-10-9885.js

4347-324-10-9885.js

60 ms

forms2.css

forms2.css

8 ms

forms2-theme-simple.css

forms2-theme-simple.css

41 ms

83 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

159 ms

ad_status.js

ad_status.js

157 ms

adsct

adsct

219 ms

Pug

Pug

188 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

175 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

190 ms

c

c

245 ms

cb

cb

148 ms

XDFrame

XDFrame

174 ms

pixel

pixel

29 ms

sd

sd

11 ms

cb

cb

3 ms

ncm

ncm

4 ms

forms2.min.js

forms2.min.js

12 ms

cb

cb

28 ms

tap.php

tap.php

1091 ms

application2.js

application2.js

111 ms

storage.html

storage.html

127 ms

storage.js

storage.js

30 ms

visits

visits

174 ms

jquery.js

jquery.js

33 ms

91971508380332b72bdbd4e76ff0d4b4.css

91971508380332b72bdbd4e76ff0d4b4.css

43 ms

2-textmarks-354329.css

2-textmarks-354329.css

36 ms

Accessibility Review

textmarks.com accessibility score

80

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

textmarks.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

textmarks.com SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Textmarks.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Textmarks.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

textmarks.com

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