Tools & Wizards About Us
taggify.net screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

taggify.net

Programmatic Digital Out of Home Platform

Page Load Speed

863 ms in total

First Response

68 ms

Resources Loaded

424 ms

Page Rendered

371 ms

taggify.net screenshot

About Website

Visit taggify.net now to see the best up-to-date Taggify content for Argentina and also check out these interesting facts you probably never knew about taggify.net

Taggify is the first programmatic DOOH platform. We connect advertisers with media owners to run programmatic DOOH campaigns.

Visit taggify.net

Key Findings

We analyzed Taggify.net page load time and found that the first response time was 68 ms and then it took 795 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

taggify.net performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value20.8 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value6,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

taggify.net

68 ms

style.css

11 ms

animate.min.css

14 ms

nivo-lightbox.min.css

13 ms

default.min.css

15 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 65% of them (33 requests) were addressed to the original Taggify.net, 20% (10 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (305 ms) relates to the external source Codes.taggify.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (33%)

Content Size

3.6 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Taggify.net main page is 3.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 37.2 kB

  • Original 52.0 kB
  • After minification 48.4 kB
  • After compression 14.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.2 kB or 71% of the original size.

Image Optimization

-30%

Potential reduce by 1.0 MB

  • Original 3.4 MB
  • After minification 2.3 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. Obviously, Taggify needs image optimization as it can save up to 1.0 MB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 32.6 kB

  • Original 54.2 kB
  • After minification 54.2 kB
  • After compression 21.6 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 32.6 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 99.3 kB

  • Original 116.9 kB
  • After minification 112.2 kB
  • After compression 17.6 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. Taggify.net needs all CSS files to be minified and compressed as it can save up to 99.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (41%)

Requests Now

39

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

taggify.net

taggify.net

68 ms

style.css

style.css

11 ms

animate.min.css

animate.min.css

14 ms

nivo-lightbox.min.css

nivo-lightbox.min.css

13 ms

default.min.css

default.min.css

15 ms

font-awesome.css

font-awesome.css

29 ms

css

css

41 ms

css

css

53 ms

modernizr.custom.js

modernizr.custom.js

13 ms

jquery-2.0.3.min.js

jquery-2.0.3.min.js

25 ms

jquery.cookie.min.js

jquery.cookie.min.js

41 ms

jquery.easing.min.js

jquery.easing.min.js

23 ms

jquery.scrollTo.js

jquery.scrollTo.js

23 ms

jquery.form.js

jquery.form.js

25 ms

main.js

main.js

30 ms

waypoints.min.js

waypoints.min.js

30 ms

owl.carousel.min.js

owl.carousel.min.js

29 ms

nivo-lightbox.min.js

nivo-lightbox.min.js

29 ms

pixel.php

pixel.php

305 ms

logo.png

logo.png

42 ms

analytics.js

analytics.js

22 ms

homescreen_dashboard.png

homescreen_dashboard.png

9 ms

computer_sample.png

computer_sample.png

93 ms

screen_dashboard.png

screen_dashboard.png

9 ms

features-gallery-reach-geos.png

features-gallery-reach-geos.png

7 ms

features-gallery-reach-devices.png

features-gallery-reach-devices.png

6 ms

features-gallery-reach-tos.png

features-gallery-reach-tos.png

7 ms

features-gallery-reach-verticals.png

features-gallery-reach-verticals.png

11 ms

gallery-01-login.png

gallery-01-login.png

94 ms

gallery-02-first-screen.png

gallery-02-first-screen.png

92 ms

gallery-03-campaign-1.png

gallery-03-campaign-1.png

90 ms

gallery-04-campaign-2.png

gallery-04-campaign-2.png

90 ms

gallery-05-ads-creation.png

gallery-05-ads-creation.png

92 ms

gallery-06-ads-url-builder.png

gallery-06-ads-url-builder.png

94 ms

gallery-07-ads-manage.png

gallery-07-ads-manage.png

97 ms

gallery-08-billings-funds.png

gallery-08-billings-funds.png

97 ms

gallery-09-billings-stripe.png

gallery-09-billings-stripe.png

100 ms

gallery-10-billings-budget.png

gallery-10-billings-budget.png

95 ms

gallery-11-dashboard-bidding.png

gallery-11-dashboard-bidding.png

99 ms

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

91 ms

toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf

toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf

91 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

99 ms

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

99 ms

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

98 ms

toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf

toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf

98 ms

collect

collect

20 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

22 ms

zJY4gsxBiSo5L7tNutxFNg.ttf

zJY4gsxBiSo5L7tNutxFNg.ttf

20 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

28 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

28 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2 ms

Accessibility Review

taggify.net accessibility score

94

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-hidden="true"] elements contain focusable descendents

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

Best Practices

taggify.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

taggify.net SEO score

96

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

High

Tap targets are not sized appropriately

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 Taggify.net 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 Taggify.net 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

taggify.net

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