Tools & Wizards About Us
trendslide.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

trendslide.com

Domain Name System (DNS) | Oracle

Page Load Speed

3 sec in total

First Response

33 ms

Resources Loaded

2.7 sec

Page Rendered

213 ms

trendslide.com screenshot

About Website

Visit trendslide.com now to see the best up-to-date Trendslide content and also check out these interesting facts you probably never knew about trendslide.com

The Domain Name System (DNS) is a distributed internet system that maps human-readable names (like www.Oracle.com) to IP addresses. Oracle's globally distributed DNS service offers enhanced DNS perfor...

Visit trendslide.com

Key Findings

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

Performance Metrics

trendslide.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value3,110 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.594

11/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

trendslide.com

33 ms

400 ms

2573310155.js

31 ms

dyn-uikit.css

28 ms

style.css

18 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Trendslide.com, 18% (23 requests) were made to Dyn.com and 12% (15 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (478 ms) relates to the external source Adverts.adgenie.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (71%)

Content Size

1.5 MB

After Optimization

432.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trendslide.com main page is 1.5 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. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 49.6 kB

  • Original 65.5 kB
  • After minification 60.2 kB
  • After compression 15.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. 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 49.6 kB or 76% of the original size.

Image Optimization

-6%

Potential reduce by 3.7 kB

  • Original 57.8 kB
  • After minification 54.1 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. Trendslide images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 727.4 kB

  • Original 1.1 MB
  • After minification 864.6 kB
  • After compression 327.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 727.4 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 261.8 kB

  • Original 296.5 kB
  • After minification 185.7 kB
  • After compression 34.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. Trendslide.com needs all CSS files to be minified and compressed as it can save up to 261.8 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 74 (84%)

Requests Now

88

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trendslide.com

trendslide.com

33 ms

400 ms

2573310155.js

2573310155.js

31 ms

dyn-uikit.css

dyn-uikit.css

28 ms

style.css

style.css

18 ms

jquery.js

jquery.js

257 ms

uikit.js

uikit.js

278 ms

jquery-migrate-1.2.1.js

jquery-migrate-1.2.1.js

19 ms

scroll.js

scroll.js

20 ms

dynevents.min.js

dynevents.min.js

24 ms

ip.json

ip.json

289 ms

event

event

234 ms

geo2.js

geo2.js

157 ms

event

event

253 ms

evergage.min.js

evergage.min.js

249 ms

6W7BE-M5LXH-CTY93-2NS7S-Z92YG

6W7BE-M5LXH-CTY93-2NS7S-Z92YG

148 ms

MasterTMS.min.js

MasterTMS.min.js

142 ms

retina-dyn-sprite.png

retina-dyn-sprite.png

96 ms

ip4d.jpg

ip4d.jpg

96 ms

exp-latency.jpg

exp-latency.jpg

95 ms

WB061_Homepage.jpg

WB061_Homepage.jpg

96 ms

AvenirLTW04_35Light.woff

AvenirLTW04_35Light.woff

95 ms

AvenirLTW04_95Black.woff

AvenirLTW04_95Black.woff

93 ms

main-02.min.js

main-02.min.js

52 ms

site-scripts.js

site-scripts.js

55 ms

gtm.js

gtm.js

55 ms

SourceSansPro-Light.woff

SourceSansPro-Light.woff

228 ms

SourceSansPro-ExtraLight.woff

SourceSansPro-ExtraLight.woff

229 ms

SourceSansPro-Regular.woff

SourceSansPro-Regular.woff

226 ms

SourceSansPro-Semibold.woff

SourceSansPro-Semibold.woff

229 ms

SourceSansPro-Bold.woff

SourceSansPro-Bold.woff

223 ms

SourceSansPro-Black.woff

SourceSansPro-Black.woff

224 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

229 ms

event

event

213 ms

tags

tags

176 ms

twreceiver

twreceiver

85 ms

conversion_async.js

conversion_async.js

50 ms

roundtrip.js

roundtrip.js

41 ms

analytics.js

analytics.js

41 ms

munchkin.js

munchkin.js

111 ms

plusone.js

plusone.js

158 ms

dyn.beacon.min.js

dyn.beacon.min.js

123 ms

bizible.js

bizible.js

178 ms

tag.js

tag.js

102 ms

code.js

code.js

225 ms

4yYUFLVN.min.js

4yYUFLVN.min.js

101 ms

spx

spx

168 ms

munchkin.js

munchkin.js

17 ms

ip.json

ip.json

28 ms

pixel

pixel

69 ms

collect

collect

126 ms

visitWebPage

visitWebPage

187 ms

collect

collect

67 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

80 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

115 ms

fastbutton

fastbutton

156 ms

pixel

pixel

53 ms

capture-apps-3.0.2.js

capture-apps-3.0.2.js

31 ms

110 ms

spx

spx

110 ms

spx

spx

109 ms

st

st

150 ms

AO4PQEZMUZGV3DXPCUMKPU.js

AO4PQEZMUZGV3DXPCUMKPU.js

193 ms

yieldify_1457450204.js

yieldify_1457450204.js

96 ms

ga-audiences

ga-audiences

136 ms

postmessageRelay

postmessageRelay

90 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

56 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

54 ms

st

st

102 ms

gs

gs

182 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

34 ms

rpc:shindig_random.js

rpc:shindig_random.js

32 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

15 ms

fbevents.hashing.js

fbevents.hashing.js

32 ms

39 ms

42 ms

42 ms

49 ms

48 ms

41 ms

73 ms

73 ms

72 ms

71 ms

72 ms

71 ms

85 ms

out

out

23 ms

out

out

23 ms

out

out

23 ms

out

out

23 ms

out

out

37 ms

out

out

44 ms

out

out

44 ms

u.php

u.php

90 ms

adsct

adsct

133 ms

61 ms

129 ms

65 ms

63 ms

64 ms

72 ms

pixel

pixel

70 ms

68 ms

generic

generic

46 ms

54 ms

56 ms

53 ms

52 ms

63 ms

63 ms

sync

sync

20 ms

52 ms

tap.php

tap.php

23 ms

sd

sd

8 ms

377928.gif

377928.gif

11 ms

generic

generic

7 ms

in

in

13 ms

st

st

83 ms

ipv

ipv

55 ms

504175.js

504175.js

291 ms

genieTracker.php

genieTracker.php

478 ms

BizibleAcct.js

BizibleAcct.js

97 ms

u

u

56 ms

genieTracker.php

genieTracker.php

415 ms

Accessibility Review

trendslide.com accessibility score

48

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 match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

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

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

trendslide.com SEO score

84

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trendslide.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 Trendslide.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

trendslide.com

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